Document problems with Windows file names that end in blanks.

 doc/lispref/files.texi (Information about Files): Mention file names with
 trailing blanks on MS-Windows.  (Bug#15130)

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 3f9d23a5476ec4d87ed1429b89018a79f0b6a568..d2e86c25cc17ed45ed0f299fc66d0ff3f7934f44 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2013-08-20  Eli Zaretskii  <eliz@gnu.org>
+
+       * files.texi (Information about Files): Mention file names with
+       trailing blanks on MS-Windows.  (Bug#15130)
+
 2013-08-18  Xue Fuqiao  <xfq.free@gmail.com>
 
        * positions.texi (Positions): Improve indexing.

diff --git a/doc/lispref/files.texi b/doc/lispref/files.texi
index 77b097ae90a077e0c536b6c6f1bca2ff1353fa74..1f7169522cce6bb5382edb69b325e90c06663948 100644 (file)
--- a/doc/lispref/files.texi
+++ b/doc/lispref/files.texi
@@ -776,6 +776,14 @@ return information about actual files or directories, so their
 arguments must all exist as actual files or directories unless
 otherwise noted.
 
+@cindex file names, trailing whitespace
+@cindex trailing blanks in file names
+Be careful with file names that end in blanks: some filesystems
+(notably, MS-Windows) will ignore trailing whitespace in file names,
+and return information about the file after stripping those blanks
+from the name, not about the file whose name you passed to the
+functions described in this section.
+
 @menu
 * Testing Accessibility::   Is a given file readable?  Writable?
 * Kinds of Files::          Is it a directory?  A symbolic link?