mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2025-01-05 11:45:45 +00:00
Code Issues Releases Activity

(Undo): Update description of `undo-outer-limit'.

Browse Source
This commit is contained in:
Luc Teirlinck 2005-01-31 23:18:45 +00:00
parent fb89c33096
commit 23c5319c0e
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man/basic.texi
View File

@ -399,13 +399,13 @@ value of @code{undo-strong-limit} is 30000.
Regardless of the values of those variables, the most recent change
is never discarded unless it gets bigger than @code{undo-outer-limit}
(normally 300,000). At that point, Emacs asks whether to discard the
undo information even for the current command. (You also have the
option of quitting.) So there is normally no danger that garbage
collection occurring right after an unintentional large change might
prevent you from undoing it. But if you didn't expect the command
to create such large undo data, you can get rid of it and prevent
Emacs from running out of memory.
(normally 3,000,000). At that point, Emacs discards the undo data and
warns you about it. This is the only situation in which you can not
undo the last command. If this happens, you can increase the value of
@code{undo-outer-limit} to make it even less likely to happen in the
future. But if you didn't expect the command to create such large
undo data, then it is probably a bug and you should report it.
@xref{Bugs,, Reporting Bugs}.
The reason the @code{undo} command has two keys, @kbd{C-x u} and
@kbd{C-_}, set up to run it is that it is worthy of a single-character