aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2001-04-30 13:35:05 +0000
committerEli Zaretskii2001-04-30 13:35:05 +0000
commit4691d21ee4eec5292193f870f936bb65481ea40d (patch)
treebda08c2db1891737d5ed4b223affa0279de22402
parent50df7214b3defc0705f2c776d5659c97925673ce (diff)
downloademacs-4691d21ee4eec5292193f870f936bb65481ea40d.tar.gz
emacs-4691d21ee4eec5292193f870f936bb65481ea40d.zip
(Marks vs Flags): Explain that dired-undo doesn't undo the file
operations. (Transforming File Names): Document that these commands operate on ARG or marked files, and that they ask for confirmation on each file.
-rw-r--r--man/dired.texi26
1 files changed, 23 insertions, 3 deletions
diff --git a/man/dired.texi b/man/dired.texi
index 92316f98642..761c52215fd 100644
--- a/man/dired.texi
+++ b/man/dired.texi
@@ -437,7 +437,12 @@ name.
437@kindex C-_ @r{(Dired)} 437@kindex C-_ @r{(Dired)}
438@findex dired-undo 438@findex dired-undo
439Undo changes in the Dired buffer, such as adding or removing 439Undo changes in the Dired buffer, such as adding or removing
440marks (@code{dired-undo}). 440marks (@code{dired-undo}). @emph{This command does not revert the
441actual file operations, nor recovers lost files!} It just undoes
442changes in the buffer itself. For example, if used after renaming one
443or more files, @code{dired-undo} restores the original names, which
444will get the Dired buffer out of sync with the actual contents of the
445directory.
441@end table 446@end table
442 447
443@node Operating on Files 448@node Operating on Files
@@ -684,7 +689,21 @@ Updating}).
684@node Transforming File Names 689@node Transforming File Names
685@section Transforming File Names in Dired 690@section Transforming File Names in Dired
686 691
687 Here are commands that alter file names in a systematic way: 692 This section describes Dired commands which alter file names in a
693systematic way.
694
695 Like the basic Dired file-manipulation commands (@pxref{Operating on
696Files}), the commands described here operate either on the next
697@var{n} files, or on all files marked with @samp{*}, or on the current
698file. (To mark files, use the commands described in @ref{Marks vs
699Flags}.)
700
701 All of the commands described in this section work
702@emph{interactively}: they ask you to confirm the operation for each
703candidate file. Thus, you can select more files than you actually
704need to operate on (e.g., with a regexp that matches many files), and
705then refine the selection by typing @kbd{y} or @kbd{n} when the
706command prompts for confirmation.
688 707
689@table @kbd 708@table @kbd
690@findex dired-upcase 709@findex dired-upcase
@@ -742,7 +761,8 @@ matches that should span the whole filename.)
742 Normally, the replacement process does not consider the files' 761 Normally, the replacement process does not consider the files'
743directory names; it operates on the file name within the directory. If 762directory names; it operates on the file name within the directory. If
744you specify a numeric argument of zero, then replacement affects the 763you specify a numeric argument of zero, then replacement affects the
745entire absolute file name including directory name. 764entire absolute file name including directory name. (Non-zero
765argument specifies the number of files to operate on.)
746 766
747 Often you will want to select the set of files to operate on using the 767 Often you will want to select the set of files to operate on using the
748same @var{regexp} that you will use to operate on them. To do this, 768same @var{regexp} that you will use to operate on them. To do this,