unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: highlight regular expression in grep window
Date: Thu, 05 Sep 2013 00:47:17 -0600	[thread overview]
Message-ID: <l099bo$j98$1@ger.gmane.org> (raw)
In-Reply-To: <cdae1429-678d-48dc-a7b1-a2a5dfc39c2f@default>

On 9/4/13 2:33 PM, Drew Adams wrote:
>> My customized grep function is something like:
>>
>> find . -type d \( -name unix -o -name "*_sim" -o -name RCS -o -name CVS -o -
>> name SCCS \) -prune -o -type f \! -name \*\~ \! -name \*\,v \! -name s.\* \!
>> -name .\#\* -name \*.\[sch\] -print | xargs -e grep -n -i  mem_test
>> /dev/null
>
> Ah, so this is not about `M-x grep'.  I guess it's about `grep-find'.
> Still, repeating the command and using `M-p' should show you the previous
> command used, including its regexp.
...
> The regexp you typed was not seen as such by Emacs.  All that was seen was
> the entire input command, including that regexp.  To extract the regexp I
> think you would need to add code that matches that input against the template
> `grep-find-command', which has the hole into which you inserted the regexp.
>
> Maybe someone else can help more; sorry.

rgrep is an interactive autoloaded Lisp function in `grep.el'.

(rgrep REGEXP &optional FILES DIR CONFIRM)

Recursively grep for REGEXP in FILES in directory tree rooted at DIR.
The search is limited to file names matching shell pattern FILES.
FILES may use abbreviations defined in `grep-files-aliases', e.g.
entering `ch' is equivalent to `*.[ch]'.

With C-u prefix, you can edit the constructed shell command line
before it is executed.
With two C-u prefixes, directly edit and run `grep-find-command'.

Collect output in a buffer.  While find runs asynchronously, you
can use C-x ` (M-x next-error), or
Uses keymap "grep-mode-map", which is not currently defined.
M-x compile-goto-error in the grep output buffer,
to go to the lines where grep found matches.

This command shares argument histories with M-x lgrep and M-x grep-find.

-- 
Kevin Rodgers
Denver, Colorado, USA




  reply	other threads:[~2013-09-05  6:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 17:47 highlight regular expression in grep window Rami A
2013-09-04 18:48 ` Drew Adams
     [not found] ` <mailman.1313.1378320529.10748.help-gnu-emacs@gnu.org>
2013-09-04 19:32   ` Rami A
2013-09-04 20:33     ` Drew Adams
2013-09-05  6:47       ` Kevin Rodgers [this message]
     [not found]     ` <mailman.1317.1378326833.10748.help-gnu-emacs@gnu.org>
2014-02-08 19:46       ` Rami A
2014-02-08 22:19         ` Drew Adams
2014-02-08 22:33 ` Rami A
2014-02-08 22:50   ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='l099bo$j98$1@ger.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=help-gnu-emacs@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).