mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2025-01-06 11:55:48 +00:00
(Undo): Update description of `undo-outer-limit'.
This commit is contained in:
parent
fb89c33096
commit
23c5319c0e
@ -399,13 +399,13 @@ value of @code{undo-strong-limit} is 30000.
|
|||||||
|
|
||||||
Regardless of the values of those variables, the most recent change
|
Regardless of the values of those variables, the most recent change
|
||||||
is never discarded unless it gets bigger than @code{undo-outer-limit}
|
is never discarded unless it gets bigger than @code{undo-outer-limit}
|
||||||
(normally 300,000). At that point, Emacs asks whether to discard the
|
(normally 3,000,000). At that point, Emacs discards the undo data and
|
||||||
undo information even for the current command. (You also have the
|
warns you about it. This is the only situation in which you can not
|
||||||
option of quitting.) So there is normally no danger that garbage
|
undo the last command. If this happens, you can increase the value of
|
||||||
collection occurring right after an unintentional large change might
|
@code{undo-outer-limit} to make it even less likely to happen in the
|
||||||
prevent you from undoing it. But if you didn't expect the command
|
future. But if you didn't expect the command to create such large
|
||||||
to create such large undo data, you can get rid of it and prevent
|
undo data, then it is probably a bug and you should report it.
|
||||||
Emacs from running out of memory.
|
@xref{Bugs,, Reporting Bugs}.
|
||||||
|
|
||||||
The reason the @code{undo} command has two keys, @kbd{C-x u} and
|
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
|
@kbd{C-_}, set up to run it is that it is worthy of a single-character
|
||||||
|
Loading…
Reference in New Issue
Block a user