X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/2626389a87c4f67809cfdd887a82e810a109576f..937640a621a4ce2e5e56eaecca37a2a28a584318:/man/emacs-xtra.texi

diff --git a/man/emacs-xtra.texi b/man/emacs-xtra.texi
index c5a601f06b..9dff3d9efd 100644
--- a/man/emacs-xtra.texi
+++ b/man/emacs-xtra.texi
@@ -8,7 +8,7 @@
 @comment %**end of header
 
 @copying
-This file describes specialized features of Emacs.
+This manual describes specialized features of Emacs.
 
 Copyright (C) 2004
 Free Software Foundation, Inc.
@@ -143,8 +143,9 @@ automatically erasing the marks.
 @node Auto Reverting Dired
 @section Auto Reverting Dired buffers
 
-Auto-reverting Dired buffers currently only works satisfactorily on
-GNU/Linux and Unix style operating systems.
+Auto-reverting Dired buffers currently works on GNU or Unix style
+operating systems.  It may not work satisfactorily on some other
+systems.
 
 Dired buffers only auto-revert when the file list of the buffer's main
 directory changes.  They do not auto-revert when information about a
@@ -161,16 +162,15 @@ not guaranteed.
 If the Dired buffer is marked modified and there are no changes you
 want to protect, then most of the time you can make auto-reverting
 resume by manually reverting the buffer using @kbd{g}.  There is one
-exception.  If you flag or mark files, then, unlike for the Buffer
-Menu, you can safely revert the buffer.  This will not erase the flags
-or marks (unless the marked file has been deleted, of course).
-However, the buffer will stay modified, even after reverting, and
-auto-reverting will not resume.  This is because, if you flag or mark
-files, you may be working on the buffer and you might not want the
-buffer to change without warning.  If you want auto-reverting to
-resume in the presence of marks and flags, mark the buffer
-non-modified using @kbd{M-~}.  However, adding, deleting or changing
-marks or flags will mark it modified again.
+exception.  If you flag or mark files, you can safely revert the
+buffer.  This will not erase the flags or marks (unless the marked
+file has been deleted, of course).  However, the buffer will stay
+modified, even after reverting, and auto-reverting will not resume.
+This is because, if you flag or mark files, you may be working on the
+buffer and you might not want the buffer to change without warning.
+If you want auto-reverting to resume in the presence of marks and
+flags, mark the buffer non-modified using @kbd{M-~}.  However, adding,
+deleting or changing marks or flags will mark it modified again.
 
 Remote Dired buffers are not auto-reverted.  Neither are Dired buffers
 for which you used shell wildcards or file arguments to list only some
@@ -253,6 +253,9 @@ mode for auto-reverting often involves getting rid of such messages.
 This is especially important for buffers that automatically
 auto-revert every @code{auto-revert-interval} seconds.
 
+Also, you may want to update the documentation string of
+@code{global-auto-revert-non-file-buffers}.
+
 @ifinfo
 Finally, you should add a node to this chapter's menu.  This node
 @end ifinfo
@@ -288,6 +291,12 @@ its old switches.  However, reverting the buffer will relist it using
 the buffer's default switches.  If any of this yields problems, you
 can easily correct the situation using @kbd{C-u i} or @kbd{C-u l}.
 
+Dired does not remember the @code{R} switch.  Inserting a subdirectory
+with switches that include the @code{R} switch is equivalent with
+inserting each of its subdirectories using all remaining switches.
+For instance, updating or killing a subdirectory that was inserted
+with the @code{R} switch will not update or kill its subdirectories.
+
 The buffer's default switches do not affect subdirectories that were
 inserted using explicitly specified switches.  In particular,
 commands such as @kbd{s}, that change the buffer's switches do not
@@ -304,3 +313,7 @@ all subdirectories with the buffer's default switches using
 @printindex cp
 
 @bye
+
+@ignore
+   arch-tag: 75c33f13-32c6-41b6-9537-847a312e2e49
+@end ignore