aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2005-02-03 07:20:07 +0000
committerRichard M. Stallman2005-02-03 07:20:07 +0000
commit7f9c94b0881d5089d66d1706cfec60f97745c3c2 (patch)
treeba7157c60a1f71f110c6399cbe9de6850f9f53e5
parentae473bd3ef47ac71101961bb91d3debfdc600d0d (diff)
downloademacs-7f9c94b0881d5089d66d1706cfec60f97745c3c2.tar.gz
emacs-7f9c94b0881d5089d66d1706cfec60f97745c3c2.zip
(Undo): Clarify last change.
-rw-r--r--man/basic.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/basic.texi b/man/basic.texi
index 29bf6d4e207..1598de2632a 100644
--- a/man/basic.texi
+++ b/man/basic.texi
@@ -400,7 +400,7 @@ value of @code{undo-strong-limit} is 30000.
400 Regardless of the values of those variables, the most recent change 400 Regardless of the values of those variables, the most recent change
401is never discarded unless it gets bigger than @code{undo-outer-limit} 401is never discarded unless it gets bigger than @code{undo-outer-limit}
402(normally 3,000,000). At that point, Emacs discards the undo data and 402(normally 3,000,000). At that point, Emacs discards the undo data and
403warns you about it. This is the only situation in which you can not 403warns you about it. This is the only situation in which you cannot
404undo the last command. If this happens, you can increase the value of 404undo the last command. If this happens, you can increase the value of
405@code{undo-outer-limit} to make it even less likely to happen in the 405@code{undo-outer-limit} to make it even less likely to happen in the
406future. But if you didn't expect the command to create such large 406future. But if you didn't expect the command to create such large