emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Grep Searching node in building.texi


From: Juri Linkov
Subject: Grep Searching node in building.texi
Date: Thu, 04 Aug 2005 05:14:03 +0300
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

I checked the node `Grep Searching' and want to propose the following
corrections.  I think mentioning the `-nH' option is essential
(and also I find the phrase `where there were' too clumsy).

Index: man/building.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/man/building.texi,v
retrieving revision 1.65
diff -c -r1.65 building.texi
*** man/building.texi   23 Jun 2005 01:22:28 -0000      1.65
--- man/building.texi   4 Aug 2005 02:12:08 -0000
***************
*** 325,337 ****
  
  @findex grep
    Just as you can run a compiler from Emacs and then visit the lines
! where there were compilation errors, you can also run @code{grep} and
  then visit the lines on which matches were found.  This works by
  treating the matches reported by @code{grep} as if they were ``errors.''
  
    To do this, type @kbd{M-x grep}, then enter a command line 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 figures out the tag
--- 325,340 ----
  
  @findex grep
    Just as you can run a compiler from Emacs and then visit the lines
! with compilation errors, you can also run @code{grep} and
  then visit the lines on which matches were found.  This works by
  treating the matches reported by @code{grep} as if they were ``errors.''
  
    To do this, type @kbd{M-x grep}, then enter a command line that
  specifies how to run @code{grep}.  Use the same arguments you would give
! @code{grep} when running it normally: the @samp{-nH} options to
! print the filename and the line number (without these options you
! will not be able to visit matches in the source file from
! the @code{grep} output buffer) and 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 figures out the tag

-- 
Juri Linkov
http://www.jurta.org/emacs/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]