Commit b575e44c authored by Eli Zaretskii's avatar Eli Zaretskii
Browse files

Fix documentation of a recent changeset

* lisp/autorevert.el (auto-revert-mode):
* lisp/files.el (revert-buffer): Doc fix.  (Bug#49661)
parent 6bea195d
Pipeline #11501 failed with stages
in 11 seconds
......@@ -391,10 +391,9 @@ disk changes.
When a buffer is reverted, a message is generated. This can be
suppressed by setting `auto-revert-verbose' to nil.
Reverting may also break markers in the buffer. To avoid that
you may set `revert-buffer-insert-file-contents-function' to the
slower function `revert-buffer-insert-file-contents-delicately'.
See its description for details.
Reverting can sometimes fail to preserve all the markers in the buffer.
To avoid that, set `revert-buffer-insert-file-contents-function' to
the slower function `revert-buffer-insert-file-contents-delicately'.
Use `global-auto-revert-mode' to automatically revert all buffers.
Use `auto-revert-tail-mode' if you know that the file will only grow
......@@ -6278,10 +6278,6 @@ This undoes all changes since the file was visited or saved.
With a prefix argument, offer to revert from latest auto-save file, if
that is more recent than the visited file.
Reverting a buffer will try to preserve markers in the buffer,
but for better results see `revert-buffer-with-fine-grain'. For
details see the Info node `(elisp)Reverting'.
This command also implements an interface for special buffers
that contain text that doesn't come from a file, but reflects
some other data instead (e.g. Dired buffers, `buffer-list'
......@@ -6307,7 +6303,12 @@ This function binds `revert-buffer-in-progress-p' non-nil while it operates.
This function calls the function that `revert-buffer-function' specifies
to do the work, with arguments IGNORE-AUTO and NOCONFIRM.
The default function runs the hooks `before-revert-hook' and
Reverting a buffer will try to preserve markers in the buffer,
but it cannot always preserve all of them. For better results,
use `revert-buffer-with-fine-grain', which tries harder to
preserve markers and overlays, at the price of being slower."
;; I admit it's odd to reverse the sense of the prefix argument, but
;; there is a lot of code out there that assumes that the first
;; argument should be t to avoid consulting the auto-save file, and
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment