summaryrefslogtreecommitdiffstats
path: root/doc/filename.n
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2024-06-11 12:13:54 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2024-06-11 12:13:54 (GMT)
commitb67bee2a5ef32b3377cebaa30c9ddbd1067f05e0 (patch)
tree7505fba0f488a1dd043bfbf51b5806504f5d09d6 /doc/filename.n
parent7546332ccf74bd863948ec07c404e163023ee445 (diff)
downloadtcl-b67bee2a5ef32b3377cebaa30c9ddbd1067f05e0.zip
tcl-b67bee2a5ef32b3377cebaa30c9ddbd1067f05e0.tar.gz
tcl-b67bee2a5ef32b3377cebaa30c9ddbd1067f05e0.tar.bz2
Backport: Another round of small fixes, especially spelling errors...
Diffstat (limited to 'doc/filename.n')
-rw-r--r--doc/filename.n14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/filename.n b/doc/filename.n
index d8a3364..0520677 100644
--- a/doc/filename.n
+++ b/doc/filename.n
@@ -41,6 +41,7 @@ The rules for native names depend on the value reported in the Tcl
\fBplatform\fR element of the \fBtcl_platform\fR array:
.TP 10
\fBUnix\fR
+.
On Unix and Apple MacOS X platforms, Tcl uses path names where the
components are separated by slashes. Path names may be relative or
absolute, and file names may contain any character other than slash.
@@ -58,28 +59,35 @@ The following examples illustrate various forms of path
names:
.TP 15
\fB/\fR
+.
Absolute path to the root directory.
.TP 15
\fB/etc/passwd\fR
+.
Absolute path to the file named \fBpasswd\fR in the directory
\fBetc\fR in the root directory.
.TP 15
\fB\&.\fR
+.
Relative path to the current directory.
.TP 15
\fBfoo\fR
+.
Relative path to the file \fBfoo\fR in the current directory.
.TP 15
\fBfoo/bar\fR
+.
Relative path to the file \fBbar\fR in the directory \fBfoo\fR in the
current directory.
.TP 15
\fB\&../foo\fR
+.
Relative path to the file \fBfoo\fR in the directory above the current
directory.
.RE
.TP
\fBWindows\fR
+.
On Microsoft Windows platforms, Tcl supports both drive-relative and UNC
style names. Both \fB/\fR and \fB\e\fR may be used as directory separators
in either type of name. Drive-relative names consist of an optional drive
@@ -93,28 +101,34 @@ following examples illustrate various forms of path names:
.RS
.TP 15
\fB\&\e\eHost\eshare/file\fR
+.
Absolute UNC path to a file called \fBfile\fR in the root directory of
the export point \fBshare\fR on the host \fBHost\fR. Note that
repeated use of \fBfile dirname\fR on this path will give
\fB//Host/share\fR, and will never give just \fB//Host\fR.
.TP 15
\fBc:foo\fR
+.
Volume-relative path to a file \fBfoo\fR in the current directory on drive
\fBc\fR.
.TP 15
\fBc:/foo\fR
+.
Absolute path to a file \fBfoo\fR in the root directory of drive
\fBc\fR.
.TP 15
\fBfoo\ebar\fR
+.
Relative path to a file \fBbar\fR in the \fBfoo\fR directory in the current
directory on the current volume.
.TP 15
\fB\&\efoo\fR
+.
Volume-relative path to a file \fBfoo\fR in the root directory of the current
volume.
.TP 15
\fB\&\e\efoo\fR
+.
Volume-relative path to a file \fBfoo\fR in the root directory of the current
volume. This is not a valid UNC path, so the assumption is that the
extra backslashes are superfluous.