summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2021-01-19 13:20:39 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2021-01-19 13:20:39 (GMT)
commitf387d58e76f3ac8a528db48b000583f3c1eb21aa (patch)
tree430f028e9f439e9ff548e1206a7a3636fb804208
parent81e7dac31476b2b8ae2f1de245ac549b6a9512bd (diff)
parentafe025dc938bb19763edbf5cbf1980adf163e9c5 (diff)
downloadtcl-f387d58e76f3ac8a528db48b000583f3c1eb21aa.zip
tcl-f387d58e76f3ac8a528db48b000583f3c1eb21aa.tar.gz
tcl-f387d58e76f3ac8a528db48b000583f3c1eb21aa.tar.bz2
Merge 8.6
-rw-r--r--doc/filename.n4
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/filename.n b/doc/filename.n
index f160eff..7b9d6fa 100644
--- a/doc/filename.n
+++ b/doc/filename.n
@@ -150,9 +150,7 @@ 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.
+native path names).
.PP
On Windows platforms there are file and path length restrictions.
Complete paths or filenames longer than about 260 characters will lead