[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/building.texi,v
From: |
Richard M. Stallman |
Subject: |
[Emacs-diffs] Changes to emacs/man/building.texi,v |
Date: |
Mon, 17 Jul 2006 20:58:27 +0000 |
CVSROOT: /cvsroot/emacs
Module name: emacs
Changes by: Richard M. Stallman <rms> 06/07/17 20:58:27
Index: building.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/man/building.texi,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -b -r1.102 -r1.103
--- building.texi 5 Jul 2006 07:53:25 -0000 1.102
+++ building.texi 17 Jul 2006 20:58:27 -0000 1.103
@@ -359,9 +359,17 @@
would give @code{grep} when running it normally: a @code{grep}-style
regexp (usually in single-quotes to quote the shell's special
characters) followed by file names, which may use wildcards. If you
-specify a prefix argument for @kbd{M-x grep}, it detects the tag
-(@pxref{Tags}) around point, and puts that into the default
address@hidden command.
+specify a prefix argument for @kbd{M-x grep}, it finds the tag
+(@pxref{Tags}) in the buffer around point, and puts that into the
+default @code{grep} command.
+
+ Your command need not simply run @code{grep}; you can use any shell
+command that produces output in the same format. For instance, you
+can chain @code{grep} commands, like this:
+
address@hidden
+grep -nH -e foo *.el | grep bar | grep toto
address@hidden example
The output from @code{grep} goes in the @samp{*grep*} buffer. You
can find the corresponding lines in the original files using @address@hidden