From: Stefan Vollmar <vollmar@nf.mpg.de>
To: help-gnu-emacs@gnu.org
Subject: Re: rgrep with (some) fixed parameters
Date: Sat, 07 Jun 2008 18:37:07 +0200 [thread overview]
Message-ID: <AA3EA2D0-8B9F-47C3-B175-23E5BE13A4D6@nf.mpg.de> (raw)
In-Reply-To: <g2e5lg$oco$1@ger.gmane.org>
Dear Kevin,
On 07.06.2008, at 16:23, Kevin Rodgers wrote:
> Stefan Vollmar wrote:
>> If I do the equivalent of a
>> (setq grep-find-command "find somepath \\( -path \*/.svn \\) -prune
>> -o -type f \\( -iname \\*.cpp \\) -exec grep -nH -e {} /dev/null \
>> \;")
>> in my .emacs file,
>> C-u C-u M-x rgrep
>> does indeed use this pattern (and does not ask about anything else,
>> and I could use a keyboard shortcut for this) - so far so good.
>> However, I feel that having to look at that long-ish command every
>> time I use it, is not elegant - in particular, as I need to
>> navigate to the correct position when the find command is being
>> displayed in the minibuffer (point should be between "-e" and "{}"
>> to insert the pattern to search for). Could you help me improve on
>> this?
>
> (defun project-rgrep (regexp)
> "Run `rgrep' with REGEXP, \"*.cpp\" FILES, and \"somepath\" DIR."
> (interactive
> (progn
> (grep-compute-defaults)
> (list (grep-read-regexp))))
> (rgrep regexp "*.cpp" "somepath"))
>
> --
> Kevin Rodgers
> Denver, Colorado, USA
Wonderful - exactly what I had hoped for!
Thanks,
Stefan
--
Dr. Stefan Vollmar, Dipl.-Phys.
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213 FAX +49-221-4726-298
Tel.: +49-221-478-5713 Mobile: 0160-93874279
Email: vollmar@nf.mpg.de http://www.nf.mpg.de
next prev parent reply other threads:[~2008-06-07 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 19:26 rgrep with (some) fixed parameters Stefan Vollmar
2008-06-06 20:40 ` Peter Jones
2008-06-06 21:43 ` Stefan Vollmar
2008-06-07 14:23 ` Kevin Rodgers
2008-06-07 16:37 ` Stefan Vollmar [this message]
2008-06-06 20:54 ` Thierry Volpiatto
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=AA3EA2D0-8B9F-47C3-B175-23E5BE13A4D6@nf.mpg.de \
--to=vollmar@nf.mpg.de \
--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.
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.