Subject: 24.2.50; Outdated timestamp documentation in Elisp manual
From: Toby Cubitt <[email-masked]>
To: [email-masked]
Date: Mon, 22 Oct 2012 21:02:28 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

The documentation in the Elisp manual for `file-attributes' and for
file-modification undo-list elements hasn't been updated to match the new
high-precision timestamp format.

Patch attached.

Toby
-- 
Dr T. S. Cubitt
Mathematics and Quantum Information group
Department of Mathematics
Complutense University
Madrid, Spain

email: [email-masked]
web:   www.dr-qubit.org
=== modified file 'doc/lispref/files.texi'
--- doc/lispref/files.texi	2012-10-01 02:07:14 +0000
+++ doc/lispref/files.texi	2012-10-22 18:53:24 +0000
@@ -1220,12 +1220,13 @@
 The file's @acronym{GID}, likewise.
 
 @item
-The time of last access, as a list of two integers.
-The first integer has the high-order 16 bits of time,
-the second has the low 16 bits.  (This is similar to the
-value of @code{current-time}; see @ref{Time of Day}.)  Note that on
-some FAT-based filesystems, only the date of last access is recorded,
-so this time will always hold the midnight of the day of last access.
+The time of last access, as a list of four integers.  The first
+integer has the high-order 16 bits of the seconds, the second integer
+the low 16 bits, the third the microseconds, and the fourth the
+picoseconds.  (This is similar to the value of @code{current-time};
+see @ref{Time of Day}.)  Note that on some FAT-based filesystems, only
+the date of last access is recorded, so this time will always hold the
+midnight of the day of last access.
 
 @cindex modification time of file
 @item

=== modified file 'doc/lispref/text.texi'
--- doc/lispref/text.texi	2012-09-18 05:14:42 +0000
+++ doc/lispref/text.texi	2012-10-22 18:49:39 +0000
@@ -1233,7 +1233,7 @@
 positive, point was at the beginning of the deleted text, otherwise it
 was at the end.
 
-@item (t @var{high} . @var{low})
+@item (t @var{sec-high} @var{sec-low} @var{msec} @var{usec})
 This kind of element indicates that an unmodified buffer became
 modified.  The elements @var{high} and @var{low} are two integers, each
 recording 16 bits of the visited file's modification time as of when it