diff options
Diffstat (limited to 'doc/filename.n')
| -rw-r--r-- | doc/filename.n | 51 |
1 files changed, 29 insertions, 22 deletions
diff --git a/doc/filename.n b/doc/filename.n index c0bad63..65403bd 100644 --- a/doc/filename.n +++ b/doc/filename.n @@ -4,7 +4,7 @@ '\" See the file "license.terms" for information on usage and redistribution '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES. '\" -'\" RCS: @(#) $Id: filename.n,v 1.15 2007/07/04 13:25:54 dkf Exp $ +'\" RCS: @(#) $Id: filename.n,v 1.16 2007/10/25 14:07:32 dkf Exp $ '\" .so man.macros .TH filename n 7.5 Tcl "Tcl Built-In Commands" @@ -142,29 +142,36 @@ will be correctly substituted using the \fB$HOME\fR environment variable, just like for Unix. .SH "PORTABILITY ISSUES" .PP -Not all file systems are case sensitive, so scripts should avoid code -that depends on the case of characters in a file name. In addition, -the character sets allowed on different devices may differ, so scripts -should choose file names that do not contain special characters like: -\fB<>:?"/\e|\fR. The safest approach is to use names consisting of -alphanumeric characters only. Care should be taken with filenames -which contain spaces (common on Windows systems) and -filenames where the backslash is the directory separator (Windows -native path names). Also Windows 3.1 only supports file -names with a root of no more than 8 characters and an extension of no -more than 3 characters. +Not all file systems are case sensitive, so scripts should avoid code that +depends on the case of characters in a file name. In addition, the character +sets allowed on different devices may differ, so scripts should choose file +names that do not contain special characters like: \fB<>:?"/\e|\fR. +.\"" Reset emacs highlighting +The safest approach is to use names consisting of alphanumeric characters +only. Care should be taken with filenames which contain spaces (common on +Windows systems) and filenames where the backslash is the directory separator +(Windows native path names). Also Windows 3.1 only supports file names with a +root of no more than 8 characters and an extension of no more than 3 +characters. .PP -On Windows platforms there are file and path length restrictions. -Complete paths or filenames longer than about 260 characters will lead -to errors in most file operations. +On Windows platforms there are file and path length restrictions. Complete +paths or filenames longer than about 260 characters will lead to errors in +most file operations. .PP -Another Windows peculiarity is that any number of trailing dots '.' in -filenames are totally ignored, so, for example, attempts to create a -file or directory with a name "foo." will result in the creation of a -file/directory with name "foo". This fact is reflected in the -results of 'file normalize'. Furthermore, a file name consisting only -of dots '.........' or dots with trailing characters '.....abc' is -illegal. +Another Windows peculiarity is that any number of trailing dots +.QW "." +in filenames are totally ignored, so, for example, attempts to create a file +or directory with a name +.QW "foo." +will result in the creation of a file or directory with name +.QW "foo" . +This fact is reflected in the results of +.QW \fBfile normalize\fR . +Furthermore, a file name consisting only of dots +.QW "........." +or dots with trailing characters +.QW ".....abc" +is illegal. .SH KEYWORDS current directory, absolute file name, relative file name, volume-relative file name, portability |