summaryrefslogtreecommitdiff
path: root/man/files.texi
diff options
context:
space:
mode:
authorLuc Teirlinck <teirllm@auburn.edu>2004-04-03 03:53:28 +0000
committerLuc Teirlinck <teirllm@auburn.edu>2004-04-03 03:53:28 +0000
commit15b71e1f8ae3727bba7caeff045f7ffb32a8f68f (patch)
tree103d4859b52bd31c86f4282da0a30e67d2c1f55f /man/files.texi
parentb694166c1f52f0db4a3cb6bf960a9671d4ba5120 (diff)
downloademacs-15b71e1f8ae3727bba7caeff045f7ffb32a8f68f.tar.gz
(Reverting): Correct description of revert-buffer's handling of point.
Diffstat (limited to 'man/files.texi')
-rw-r--r--man/files.texi9
1 files changed, 4 insertions, 5 deletions
diff --git a/man/files.texi b/man/files.texi
index a7f06619288..f73d1370eba 100644
--- a/man/files.texi
+++ b/man/files.texi
@@ -855,11 +855,10 @@ of the file. To do this, use @kbd{M-x revert-buffer}, which operates on
the current buffer. Since reverting a buffer unintentionally could lose
a lot of work, you must confirm this command with @kbd{yes}.
- @code{revert-buffer} keeps point at the same distance (measured in
-characters) from the beginning of the file. If the file was edited only
-slightly, you will be at approximately the same piece of text after
-reverting as before. If you have made drastic changes, the same value of
-point in the old file may address a totally different piece of text.
+ @code{revert-buffer} tries to position point in such a way that, if
+the file was edited only slightly, you will be at approximately the
+same piece of text after reverting as before. However, if you have made
+drastic changes, point may wind up in a totally different piece of text.
Reverting marks the buffer as ``not modified'' until another change is
made.