From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [RFC] Urgrep: New ELPA submission (eventually)
Date: Mon, 12 Sep 2022 14:11:04 +0300 [thread overview]
Message-ID: <83k06897av.fsf@gnu.org> (raw)
In-Reply-To: <ab8bf017-95a8-c544-8d34-d942b5ec457e@gmail.com> (message from Jim Porter on Sun, 11 Sep 2022 21:56:04 -0700)
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Sun, 11 Sep 2022 21:56:04 -0700
>
> A while back, I made a package called Urgrep ("Universal Recursive Grep"
> - <https://github.com/jimporter/urgrep>), and now that it's pretty
> stable, I'm starting preparations to submit it to GNU ELPA. I'm not
> *quite* ready to submit it for real, but I'm reasonably close and wanted
> to get some wider feedback before I actually do submit it. If you have
> any suggestions, questions, etc, I'm happy to hear them.
>
> A brief summary: Urgrep is designed to provide a universal interface on
> top of all "recursive grep"-like commands, from ripgrep to git grep to
> the classic find+grep. I made it to solve a frustration I had with other
> similar packages: they're primarily built to support a *particular*
> searching tool, and while some can be coaxed into running with other
> tools, it doesn't always work. Even when it does, it's usually not
> seamless, especially when you add Tramp to the equation.
>
> With Urgrep, you can use *any* rgrep-like command[1]. It will
> automatically use the best tool on the system in question, so if some
> remote host doesn't have your favorite tool, it'll still work just fine.
Would it make sense to add this to grep.el, instead of having an
add-on package?
next prev parent reply other threads:[~2022-09-12 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 4:56 [RFC] Urgrep: New ELPA submission (eventually) Jim Porter
2022-09-12 9:19 ` Stefan Kangas
2022-09-12 17:05 ` Jim Porter
2022-09-12 11:11 ` Eli Zaretskii [this message]
2022-09-12 18:00 ` Jim Porter
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 4:18 Jim Porter
2022-09-12 12:58 ` Stefan Monnier
2022-09-14 4:52 ` Jim Porter
2023-02-04 17:12 ` Ergus
2023-02-04 19:44 ` Jim Porter
2023-02-04 21:37 ` Ergus
2023-02-04 22:22 ` Stefan Monnier
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=83k06897av.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.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 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.