unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [GNU ELPA] New package: Urgrep
Date: Tue, 09 May 2023 08:45:07 +0000	[thread overview]
Message-ID: <871qjpuc4s.fsf@posteo.net> (raw)
In-Reply-To: <ec958cab-ec68-ee6c-08b4-6d69e25bcc5d@gmail.com> (Jim Porter's message of "Mon, 8 May 2023 22:18:32 -0700")

Jim Porter <jporterbugs@gmail.com> writes:

> I'd like to add a new package to GNU ELPA: Urgrep[1]. I posted about
> it a while ago[2], but wasn't quite ready to submit it to GNU ELPA at
> the time. Well, now is that time! I'll quote my original message for a
> summary of what it's interesting about Urgrep:
>
>> 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. 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.
>>
>> I also added some Isearch-like bindings in the main function's prompt
>> (creatively named 'urgrep'). These all start with M-s and let you set
>> common search flags, like number of context lines. Maybe there's a
>> better way to do this; the current method seemed reasonable to me, but
>> I'm certainly open to suggestions.

Looks interesting!

> [1] https://github.com/jimporter/urgrep
> [2] https://lists.gnu.org/archive/html/emacs-devel/2022-09/msg00723.html
>
> From 9745926ef47fe52f0c94287c992637e00e849b38 Mon Sep 17 00:00:00 2001
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Mon, 8 May 2023 22:07:56 -0700
> Subject: [PATCH] * elpa-packages (urgrep): New package
>
> ---
>  elpa-packages | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/elpa-packages b/elpa-packages
> index 93f6ccc..93e6e46 100644
> --- a/elpa-packages
> +++ b/elpa-packages
> @@ -696,6 +696,9 @@
>   (uni-confusables 	:url nil
>    :readme "README.md")
>   (uniquify-files	:url nil)
> + (urgrep		:url "https://github.com/jimporter/urgrep"
> +  :readme "README.md"
> +  :ignored-files (".github" "LICENSE" "Makefile" "*-tests.el"))

Could you track these files in a .elpaignore file within the repository?

>   (url-http-ntlm 	:url nil)
>   (url-http-oauth	:url "https://git.sr.ht/~fitzsim/url-http-oauth"
>    :readme ignore)



  reply	other threads:[~2023-05-09  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  5:18 [GNU ELPA] New package: Urgrep Jim Porter
2023-05-09  8:45 ` Philip Kaludercic [this message]
2023-05-09 20:26   ` Jim Porter
2023-05-10  6:22     ` Philip Kaludercic
2023-05-10 16:22       ` Jim Porter
2023-05-10 17:30         ` Philip Kaludercic
2023-05-12 21:52           ` Richard Stallman
2023-05-12 21:59             ` Jim Porter
2023-05-13  7:09               ` Philip Kaludercic
2023-05-15 22:13               ` Richard Stallman
2023-05-16  6:29                 ` Philip Kaludercic
2023-05-17 22:27                   ` Richard Stallman
2023-05-18 13:23                     ` Philip Kaludercic
2023-05-21 21:04                       ` Richard Stallman

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=871qjpuc4s.fsf@posteo.net \
    --to=philipk@posteo.net \
    --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 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).