Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

It annoys me having used Unix in college and now working on the Windows side. What's the history behind this decision? Anyone know why it worked out this way?

share|improve this question
add comment

4 Answers

up vote 46 down vote accepted

Unix introduced / as the directory separator sometime around 1970. I don't know why this exactly character was chosen; the ancestor system Multics used >, but the designers of Unix had already used > together with < for redirection in the shell (see Why is the root directory denoted by a / sign?).

MS-DOS 2.0 introduced \ as the directory separator in the early 1980s. The reason / was not used is that MS-DOS 1.0 was already using / to introduce command-line options. It took this usage of / from CP/M, which took it from VMS. You can read a more thorough explanation of why that choice was made on Larry Osterman's blog (MS-DOS even briefly had an option to change the option character to - and the directory separator to /, but it didn't stick).

/ it is recognized by most programmer-level APIs (in all versions of DOS and Windows). So you can often, but not always get away with using / as a directory separator under Windows. A notable exception is that you can't use / as a separator after the \\? prefix which (even in Windows 7) is the only way to specify a path using Unicode or containing more than 260 characters.

Some user interface elements support / as a directory separator under Windows, but not all. Some programs just pass filenames through to the underlying API, so they support / and \ indifferently. In the command interpreter (in command.com or cmd), you can use / in many cases, but not always; this is partly dependent on the version of Windows (for example, cd /windows works in XP and 7 but did not in Windows 9x). The Explorer path entry box accepts / (at least from XP up; probably because it also accepts URLs). On the other hand, the standard file open dialog rejects slashes.

share|improve this answer
/ is recognized as a directory separator by the MS-DOS or Windows command-line. –  Tom Wijsman Aug 16 '10 at 14:05
"C:\Windows\System32>cd /windows/system" works. –  Andrew J. Brehm Aug 16 '10 at 14:11
@TomWij: Do you have a reference as to where precisely / is accepted on the command line? For example, what does dir /p do? and dir c:/p? and c:/windows/notepad.exe? and start /windows/notepad.exe? etc. (I don't have a Windows machine here to test.) –  Gilles Aug 16 '10 at 14:25
msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx - File I/O functions in the Windows API convert "/" to "\" as part of converting the name to an NT-style name, except when using the "\\?\" prefix as detailed in the following sections. - The command line uses this File I/O functions. –  Tom Wijsman Aug 16 '10 at 14:28
@TomWij, @Gilles - please keep to the topic. Complaints about downvotes and related accusations/retaliations have nothing to do with the question. Downvotes happen, for good or bad reasons. If you really feel that something is wrong, take it to meta. –  Gnoupi Aug 16 '10 at 15:44
show 4 more comments

The underlying Windows API can accept either the backslash or slash to separate directory and file components of a path, but the Microsoft convention is to use a backslash, and APIs that return paths put backslash in.

MS-DOS 2.0 copied the hierarchical file system from Unix and thus used the forward slash, but (possibly on the insistence of IBM) added the backslash to allow paths to be typed into the command shell while retaining compatibility with MS-DOS 1.0 and CP/M where the slash was the command-line option indicator.



which shows the current directory in wide format against


which runs the w file in the director dir.


share|improve this answer
add comment

For what it is worth I am researching why Unix used /. Multics preceded Unix and it used >.

If I find out it will be some more useless trivia...

share|improve this answer
According to one of the smartest Multicians I ever had the pleasure of working with; "As I recall, the Unix designers had already reserved the characters > and < to signify I/O redirection on the shell command line well before they had a multi-level file system. So when they got around to that, they had to find another character to signify pathname element separation." @CDT - Thanks. –  dbasnett Aug 17 '10 at 15:19
add comment

They based it on the flawed letter-marks-the-volume DOS-style. Multiple aliases with absoutely no guarantee for coherency for directories in the My document feature is my pet pieve, though.

share|improve this answer
The "flawed letter-marks-the-volume DOS-style" actually predates MS-DOS by several years. CP/M and later CP/M-86 both used it. They also used the "/" character as a "switch" character for command line options. The earliest versions of MS-DOS closely resembled CP/M-86 but quickly diverged. –  BillP3rd Aug 16 '10 at 14:10
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.