Path (computing)

History

Around 1970, Unix introduced the forward slash character ("/") as its directory separator. In 1981, when the original version of Microsoft DOS (MS-DOS 1.0) was released, Microsoft DOS did not support directories. A major portion of the utilities packaged with DOS came from IBM. The command line prompts of these IBM-written utilities made use of the forward slash character as a "switch" which is still existent today (as in dir /w tells the dir command to run with the wide list format option). However, on Unix the dash ("-") character is used for switches. When directory support was introduced in MS-DOS 2.0, IBM desired to keep compatibility with the original DOS utilities, and a host of other programs that had been written to use the forward slash as a switching character. Since the forward slash character already served as a switching utility, Microsoft chose the back slash character ("") which character-wise looks very similar to the forward slash character ("/") to indicate directory separation.

Absolute and relative paths

An absolute or full path points to the same location in a file system, regardless of the current working directory. To do that, it must include the root directory.

By contrast, a relative path starts from some given working directory, avoiding the need to provide the full absolute path. A filename can be considered as a relative path based at the current working directory. If the working directory is not the file's parent directory, a file not found error will result if the file is addressed by its name.

Representations of paths by operating system and shell

Japanese and Korean versions of Windows may often display the '¥' character or the '₩' character instead of the directory separator. In such cases the code for a backslash is being drawn as these characters. Very early versions of MS-DOS replaced the backslash with these glyphs on the display to make it possible to display them by programs that only understood 7-bit ASCII (other characters such as the square brackets were replaced as well, see ISO 646, Windows Codepage 932 (Japanese Shift JIS), and Codepage 949 (Korean)). Although even the first version of Windows supported the 8-bit ISO-8859-1 character set which has the Yen sign at U+00A5, and modern versions of Windows supports Unicode which has the Won sign at U+20A9, much software will continue to display backslashes found in ASCII files this way to preserve backwards compatibility.

Mac OS X, as a derivative of UNIX, uses UNIX paths internally. However, to preserve compatibility for software and familiarity for users, many portions of the GUI switch "/" typed by the user to ":" internally, and switch them back when displaying filenames (a ":" entered by the user is also changed into "/" but the inverse translation does not happen).

Uniform Naming Convention

The Microsoft Windows UNC, short for Universal Naming Convention or Uniform Naming Convention, specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer. The UNC syntax for Windows systems has the generic form:

ComputerNameSharedFolderResource

Microsoft often refers to this as a "network path".

Some Microsoft Windows interfaces also allow or require UNC syntax for WebDAV share access, rather than a URL. The UNC syntax is extended with optional components to denote use of SSL and TCP/IP port number, a WebDAV URL of http[s]://HostName[:Port]/SharedFolder/Resource becomes

HostName[@SSL][@Port]SharedFolderResource

When viewed remotely, the "SharedFolder" may have a name different from what a program on the server sees when opening "SharedFolder". Instead, the SharedFolder name consists of an arbitrary name assigned to the folder when defining its "sharing".

Some Microsoft Windows interfaces also accept the "Long UNC":

?UNCComputerNameSharedFolderResource

Microsoft Windows uses the following types of paths:

local file system (LFS), such as C:File

uniform naming convention (UNC), such as ServerVolumeFile or /<internet resource name>[Directory name] (at least in Windows 7 and later)

long UNC or UNCW, such as ?C:File or ?UNCServerVolumeFile

In versions of Windows prior to Windows XP, only the APIs that accept "Long UNC" could accept more than 260 characters.

The shell in Windows XP and Windows Vista, explorer.exe, allows path names up to 248 characters long.

Since UNCs start with two backslashes, and the backslash is also used for string escaping and in regular expressions, this can result in extreme cases of leaning toothpick syndrome: an escaped string for a regular expression matching a UNC begins with 8 backslashes – – because the string and regular expression both require escaping. This can be simplified by using raw strings, as in C#'s @"" or Python's r'\' or Perl's '\'.

POSIX pathname definition

Most Unix-like systems use a similar syntax. POSIX allows treating a path beginning with two slashes in an implementation-defined manner, though in other cases systems must treat multiple slashes as single slashes. Many applications on Unix-like systems (for example, scp, rcp and rsync) use resource definitions such as:

hostname:/directorypath/resource

or like URLs with the service name (here 'smb'):

smb://hostname/directorypath/resource

Unix style

The following worked example discusses the behavior of a Unix-style file system as it would appear from a terminal or terminal application (command-line window):

Attached to a current working directory (cwd) of:

/users/mark/

One wants to change the current working directory to:

/users/mark/bobapples

At that moment, the relative path for the desired directory can be represented as:

./bobapples

or for short:

bobapples

and the absolute path for the directory as:

/users/mark/bobapples

Given bobapples as the relative path for the directory wanted, the following may be typed at the command prompt to change the current working directory to bobapples:

cd bobapples

Two dots ("..") point upwards in the hierarchy, to indicate the parent directory; one dot (".") represents the current directory itself. Both can be components of a complex relative path (e.g., "../mark/./bobapples"), where "." alone or as the first component of such a relative path represents the working directory. (Using "./foo" to refer to a file "foo" in the current working directory can sometimes usefully distinguish it from a resource "foo" to be found in a default directory or by other means; for example, to view a specific version of a manual page instead of the one installed in the system.)

MS-DOS/Microsoft Windows style

Contrary to popular belief, the Windows system API accepts slash, and thus all the above Unix examples should work. But many applications on Windows interpret a slash for other purposes or treat it as an invalid character, and thus require you to enter backslash — notably the cmd.exe shell (often called the "terminal" as it typically runs in a terminal window). Note that many other shells available for Windows, such as tcsh and Windows PowerShell, allow the slash.

In addition "" does not indicate a single root, but instead the root of the "current disk". Indicating a file on a disk other than the current one requires prefixing a drive letter and colon. No ambiguity ensues, because colon is not a valid character in an MS-DOS filename, and thus one cannot have a file called "A:" in the current directory.

UNC names (any path starting with ?) do not support slashes.

The following examples show MS-DOS/Windows-style paths, with backslashes used to match the most common syntax:

A:TempFile.txt

This path points to a file with the name File.txt, located in the directory Temp, which in turn is located in the root directory of the drive A:.

C:..File.txt

This path refers to a file called File.txt located in the parent directory of the current directory on drive C:.

FolderSubFolderFile.txt

This path denotes a file called File.txt located in SubFolder directory which in turn is located in Folder directory which is located in the current directory of the current drive (since this example gives no drive-specification).

File.txt

This rather simple path points to a file named File.txt located in the current directory (since the path lacks a directory-specification) on the current drive (since no drive specification is present).

.COM1

This path refers to the first serial port (COM1).

This example uses a path containing slashes as directory separator. The command redirects the content of the file to the more command.

A path containing forward slashes often needs to be surrounded by double quotes to disambiguate it from command line switches.

note: CD does not work this way:

CD "[drive letter]:/Program Files" will only work from the root ([drive letter]:) directory. This appears to treat all forward slashes the same as ..

exception: Use the /D switch to change current drive in addition to changing current directory for a drive.

For example:

CD "C:.Program Files"

works the same as

CD "C:/Program Files"

Also, from a root folder:

CD "C:.Program Files.Internet Explorer"

would be treated the same as

CD "C:/Program Files/Internet Explorer"

If there is no relative path to the directory name specified with forward slashes you will get the following error:

The system cannot find the path specified.

For setting environment variables, it is sometimes necessary to provide a path that does not contain spaces in it, for instance %JAVA_HOME% defined as "C:Program FilesJava..." can cause scripts to halt when they encounter the space in the path name. To get the eight-character name Windows assigns to any directory for substitution in environment variables, use the directory listing command with the /x option one level up from the target directory. For instance, the following will get you the eight character name for all directories directly under root: