summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMauro Aranda <maurooaranda@gmail.com>2018-10-18 11:28:18 -0300
committerEli Zaretskii <eliz@gnu.org>2018-10-19 11:56:34 +0300
commitf632ecbb998ccec6442cbf1e6d76a2d63af3e9e2 (patch)
treec5dd77414d66eb8d31f0c2958a9845b4bbd5a92c
parenteb6768977effe5994b6fe3afcfa262465ba631ab (diff)
downloademacs-f632ecbb998ccec6442cbf1e6d76a2d63af3e9e2.tar.gz
Update revert-buffer documentation
* doc/emacs/files.texi (Reverting): Document that revert-buffer does keep undo history. (Bug#33084) Copyright-paperwork-exempt: yes
-rw-r--r--doc/emacs/files.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index e950767c384..c1d25af35c9 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -926,10 +926,10 @@ way that, if the file was edited only slightly, you will be at
approximately the same part of the text as before. But if you have
made major changes, point may end up in a totally different location.
- Reverting marks the buffer as not modified. It also clears the
-buffer's undo history (@pxref{Undo}). Thus, the reversion cannot be
-undone---if you change your mind yet again, you can't use the undo
-commands to bring the reverted changes back.
+ Reverting marks the buffer as not modified. However, it adds the
+reverted changes as a single modification to the buffer's undo
+history (@pxref{Undo}). Thus, after reverting, you can do @kbd{C-/}
+to bring the reverted changes back, if you happen to change your mind.
Some kinds of buffers that are not associated with files, such as
Dired buffers, can also be reverted. For them, reverting means