mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-14 18:10:32 -08:00
Small fixes in documentation.
* doc/emacs/dired.texi (Operating on Files): Fix name of dired-vc-rename-file. * doc/emacs/fixit.texi (Undo): Update new values of undo limits doubled in bug#31104.
This commit is contained in:
parent
06166aa719
commit
7dd065fc7b
2 changed files with 5 additions and 5 deletions
|
|
@ -720,8 +720,8 @@ should create non-existent directories in @var{new}.
|
|||
Dired automatically changes the visited file name of buffers associated
|
||||
with renamed files so that they refer to the new names.
|
||||
|
||||
@vindex dired-vc-rename
|
||||
If the value of the variable @code{dired-vc-rename} is non-@code{nil},
|
||||
@vindex dired-vc-rename-file
|
||||
If the value of the variable @code{dired-vc-rename-file} is non-@code{nil},
|
||||
files are renamed using the commands of the underlying VCS, via
|
||||
@code{vc-rename-file} (@pxref{VC Delete/Rename}).
|
||||
|
||||
|
|
|
|||
|
|
@ -122,14 +122,14 @@ setting the variables @code{undo-limit}, @code{undo-strong-limit}, and
|
|||
The variable @code{undo-limit} sets a soft limit: Emacs keeps undo
|
||||
data for enough commands to reach this size, and perhaps exceed it,
|
||||
but does not keep data for any earlier commands beyond that. Its
|
||||
default value is 80000. The variable @code{undo-strong-limit} sets a
|
||||
default value is 160000. The variable @code{undo-strong-limit} sets a
|
||||
stricter limit: any previous command (though not the most recent one)
|
||||
that pushes the size past this amount is forgotten. The default value
|
||||
of @code{undo-strong-limit} is 120000.
|
||||
of @code{undo-strong-limit} is 240000.
|
||||
|
||||
Regardless of the values of those variables, the most recent change
|
||||
is never discarded unless it gets bigger than @code{undo-outer-limit}
|
||||
(normally 12,000,000). At that point, Emacs discards the undo data and
|
||||
(normally 24,000,000). At that point, Emacs discards the undo data and
|
||||
warns you about it. This is the only situation in which you cannot
|
||||
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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue