@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.
all information in the buffer is up to date and does not necessarily
make manual reverts useless.
+At the other extreme, certain buffers automatically auto-revert every
+@code{auto-revert-interval} seconds. (This currently only applies to
+the Buffer Menu.) In this case, Auto Revert does not print any
+messages while reverting, even when @code{auto-revert-verbose} is
+non-@code{nil}.
+
The details depend on the particular types of buffers and are
explained in the corresponding sections.
@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
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
@noindent
in the buffer's mode function.
-The special return value @samp{fast} tells the caller that the need for
-reverting was not checked, but that reverting the buffer is fast.
-This information could be useful if the function is consulted for
-purposes other than auto-reverting.
+The special return value @samp{fast} tells the caller that the need
+for reverting was not checked, but that reverting the buffer is fast.
+It also tells Auto Revert not to print any revert messages, even if
+@code{auto-revert-verbose} is non-@code{nil}. This is important, as
+getting revert messages every @code{auto-revert-interval} seconds can
+be very annoying. The information provided by this return value could
+also be useful if the function is consulted for purposes other than
+auto-reverting.
@end defvar
Once the buffer has a @code{revert-buffer-function} and a
if @code{auto-revert-verbose} is @code{t} and effectively override a
@code{nil} value for @code{auto-revert-verbose}. Hence, adapting a
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
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
@printindex cp
@bye
+
+@ignore
+ arch-tag: 75c33f13-32c6-41b6-9537-847a312e2e49
+@end ignore