From 2d36e6a93763be8e77c763dd2011f3d037880aec Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Fri, 31 Dec 2004 15:11:01 +0000 Subject: [PATCH] (Shell Commands in Dired): Delete the ? example. --- man/dired.texi | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/man/dired.texi b/man/dired.texi index 1c5e29fe696..464aa34c6c2 100644 --- a/man/dired.texi +++ b/man/dired.texi @@ -700,26 +700,18 @@ file. 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 +replaced. @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. -- 2.39.5