From: Juri Linkov <juri@jurta.org>
Subject: Grep Searching node in building.texi
Date: Thu, 04 Aug 2005 05:14:03 +0300 [thread overview]
Message-ID: <874qa6xv68.fsf@jurta.org> (raw)
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/
next reply other threads:[~2005-08-04 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 2:14 Juri Linkov [this message]
2005-08-10 4:05 ` Grep Searching node in building.texi Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874qa6xv68.fsf@jurta.org \
--to=juri@jurta.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.