From: Jim Porter <jporterbugs@gmail.com>
To: Michael Welsh Duggan <mwd@md5i.com>, emacs-devel@gnu.org
Subject: Re: How best to set grep command based on current directory?
Date: Sat, 9 Apr 2022 15:43:22 -0700 [thread overview]
Message-ID: <494ee5b0-3b62-c8f3-dd2d-f3e10ce674c4@gmail.com> (raw)
In-Reply-To: <87a6cvkqo4.fsf@md5i.com>
On 4/8/2022 6:10 PM, Michael Welsh Duggan wrote:
> I would like to change the program invocation in "M-x grep" (or maybe
> "M-x grep-find") to default to "git grep" when in directories that are
> in git trees. I could hack away at the grep.el sources to do this, or I
> could write some advice around the grep command to do this, but I want
> to ask here, first, if anyone believes that there is a more principled
> way to make this change.
If *recursive* grep is ok (as opposed to `M-x grep'), that's what I
wrote urgrep[1] to do. It's aware of Git directories as well as remote
Tramp hosts that may have a different set of commands available for use.
I've seen using it for a while and I think I've worked out most of the
bugs. (I haven't submitted it for inclusion in GNU ELPA yet since I'm
still debating on what to do with a few parts, especially the API.)
If not, maybe the code will at least give you some ideas. After a fair
bit of experimentation, I found that the following command produces the
most consistent rgrep-like results for both Git and non-Git directories:
git grep --no-index --exclude-standard
Even within Git repos, I found the above to work best, since it searches
untracked files (excluding .gitignored files) and recurses into
submodules. The fact that it also works well for non-Git directories is
a nice bonus too.
- Jim
[1] https://github.com/jimporter/urgrep
prev parent reply other threads:[~2022-04-09 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 1:10 How best to set grep command based on current directory? Michael Welsh Duggan
2022-04-09 6:10 ` Eli Zaretskii
2022-04-09 9:22 ` Yuri Khan
2022-04-09 22:43 ` Jim Porter [this message]
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=494ee5b0-3b62-c8f3-dd2d-f3e10ce674c4@gmail.com \
--to=jporterbugs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mwd@md5i.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).