* Hiding Subdirectories:: Making subdirectories visible or invisible.
* Updating: Dired Updating. Discarding lines for files of no interest.
* Find: Dired and Find. Using `find' to choose the files for Dired.
-* Misc: Misc Dired Commands. Various other features.
+* Misc: Misc Dired Features. Various other features.
@end menu
@node Dired Enter
@findex dired
@kindex C-x d
@vindex dired-listing-switches
- To invoke Dired, do @kbd{C-x d} or @kbd{M-x dired}. The command reads
-a directory name or wildcard file name pattern as a minibuffer argument
-to specify which files to list. Where @code{dired} differs from
-@code{list-directory} is in putting the buffer into Dired mode so that
-the special commands of Dired are available.
+ To invoke Dired, do @kbd{C-x d} or @kbd{M-x dired}. The command
+reads a directory name or wildcard file name pattern as a minibuffer
+argument to specify which files to list. @kbd{C-x C-f} given a
+directory name also invokes Dired. Where @code{dired} differs from
+@code{list-directory} is that it puts the buffer into Dired mode, so
+that the special commands of Dired are available.
The variable @code{dired-listing-switches} specifies the options to
-give to @code{ls} for listing directory; this string @emph{must} contain
+give to @code{ls} for listing the directory; this string @emph{must} contain
@samp{-l}. If you use a numeric prefix argument with the @code{dired}
command, you can specify the @code{ls} switches with the minibuffer
before you enter the directory specification. No matter how they are
(move up and unflag) is often useful simply for moving up.
@findex dired-goto-file
-@kindex M-g
+@kindex M-g @r{(Dired)}
@kbd{M-g} (@code{dired-goto-file}) moves point to the line that
describes a specified file or directory.
@kindex e @r{(Dired)}
Equivalent to @kbd{f}.
+@ignore @c This command seems too risky to document at all.
@item a
@kindex a @r{(Dired)}
@findex dired-find-alternate-file
Like @kbd{f}, but replaces the contents of the Dired buffer with
that of an alternate file or directory (@code{dired-find-alternate-file}).
+@end ignore
@item o
@kindex o @r{(Dired)}
Visit the file described on the current line, and display the buffer in
another window, but do not select that window (@code{dired-display-file}).
-@item Mouse-2
+@item Mouse-1
+@itemx Mouse-2
@findex dired-mouse-find-file-other-window
Visit the file named by the line you click on
(@code{dired-mouse-find-file-other-window}). This uses another window
file.
@item
-If the command string contains @samp{?} surrounded by whitespace, the
-current file name is substituted for @samp{?}. You can use @samp{?}
-this way more than once in the command, and each occurrence is
-replaced. For instance, here is how to uuencode each file, making the
-output file name by appending @samp{.uu} to the input file name:
-
-@example
-uuencode ? ? > ?.uu
-@end example
+However, if the command string contains @samp{?} surrounded by
+whitespace, the current file name is substituted for @samp{?} (rather
+than added at the end). You can use @samp{?} this way more than once
+in the command, and the same file name replaces each occurrence.
@end itemize
To iterate over the file names in a more complicated fashion, use an
-explicit shell loop. For example, this shell command is another way
-to uuencode each file:
+explicit shell loop. For example, here is how to uuencode each file,
+making the output file name by appending @samp{.uu} to the input file
+name:
@example
for file in * ; do uuencode "$file" "$file" >"$file".uu; done
@end example
-@noindent
-This simple example doesn't require a shell loop (you can do it
-with @samp{?}, but it illustrates the technique.
-
The working directory for the shell command is the top-level directory
of the Dired buffer.
program. @kbd{M-x locate-with-filter} is similar, but keeps only lines
matching a given regular expression.
-These buffers don't work entirely like ordinary Dired buffers. File
+ These buffers don't work entirely like ordinary Dired buffers. File
operations work, but do not always automatically update the buffer.
Reverting the buffer with @kbd{g} deletes all inserted subdirectories,
and erases all flags and marks.
-@node Misc Dired Commands
-@section Other Dired Commands
+@node Misc Dired Features
+@section Other Dired Features
-@table @kbd
-@item w
@cindex Adding to the kill ring in Dired.
-@kindex w
+@kindex w @r{(Dired)}
@findex dired-copy-filename-as-kill
-The @kbd{w} command (@code{dired-copy-filename-as-kill}) puts the
+ The @kbd{w} command (@code{dired-copy-filename-as-kill}) puts the
names of the marked (or next @var{n}) files into the kill ring, as if
-you had killed them with @kbd{C-w}. With a zero prefix argument
-@var{n}=0, use the absolute file name of each marked file. With just
-@kbd{C-u} as the prefix argument, use the relative file name of each
-marked file. As a special case, if no prefix argument is given and
-point is on a directory headerline, @kbd{w} gives you the name of that
-directory without looking for marked files.
-
-@vindex dired-marked-files
-The main purpose of the @kbd{w} command is so that you can yank the
-file names into arguments for other Emacs commands. It also displays
-what was pushed onto the kill ring, so you can use it to display the
-list of currently marked files in the echo area. It also stores the
-list of names in the variable @code{dired-marked-files}, for use in
-Lisp expressions.
-@end table
+you had killed them with @kbd{C-w}.
+
+ The main purpose of this command is so that you can yank the file
+names into arguments for other Emacs commands. It also displays what
+was pushed onto the kill ring, so you can use it to display the list
+of currently marked files in the echo area. With a zero prefix
+argument @var{n}=0, this uses the absolute file name of each marked
+file. With just @kbd{C-u} as the prefix argument, it uses the
+relative file name of each marked file. As a special case, if no
+prefix argument is given and point is on a directory headerline,
+@kbd{w} gives you the name of that directory without looking for
+marked files.
+
+ On the X window system, Emacs supports the ``drag and drop''
+protocol. You can drag a file object from another program, and drop
+it onto a Dired buffer; this either moves, copies, or creates a link
+to the file in that directory. Precisely which action is taken is
+determined by the originating program. Dragging files out of a Dired
+buffer is currently not supported.
@ignore
arch-tag: d105f9b9-fc1b-4c5f-a949-9b2cf3ca2fc1