Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
6deaa218
Commit
6deaa218
authored
Apr 03, 2004
by
Luc Teirlinck
Browse files
(Reverting): Correct description of revert-buffer's handling of point.
parent
bcfa9925
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
5 deletions
+9
-5
man/ChangeLog
man/ChangeLog
+5
-0
man/files.texi
man/files.texi
+4
-5
No files found.
man/ChangeLog
View file @
6deaa218
2004-04-02 Luc Teirlinck <teirllm@auburn.edu>
* files.texi (Reverting): Correct description of revert-buffer's
handling of point.
2004-03-22 Juri Linkov <juri@jurta.org>
* emacs.texi (Top): Add `Misc X'.
...
...
man/files.texi
View file @
6deaa218
...
...
@@ -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.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment