From 7ae038f07e21a0fab4f515bb39c0340a66af1d84 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 17 Jul 2006 20:58:27 +0000 Subject: [PATCH] (Grep Searching): Explain about chaining grep commands. --- man/building.texi | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/man/building.texi b/man/building.texi index e3ca90f2863..549c69da544 100644 --- a/man/building.texi +++ b/man/building.texi @@ -359,9 +359,17 @@ that specifies how to run @code{grep}. Use the same arguments you 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 -@code{grep} 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: + +@example +grep -nH -e foo *.el | grep bar | grep toto +@end example The output from @code{grep} goes in the @samp{*grep*} buffer. You can find the corresponding lines in the original files using @w{@kbd{C-x -- 2.39.2