unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Joel Reicher <joel.reicher@gmail.com>, emacs-devel@gnu.org
Subject: Re: Should project delegate project-find-regexp?
Date: Thu, 7 Apr 2022 18:10:15 +0200	[thread overview]
Message-ID: <20220407161015.bky7j2ljqj6ebgym@Ergus> (raw)
In-Reply-To: <7147b499-0df5-6307-54ee-387f35ef9dcf@yandex.ru>

On Thu, Apr 07, 2022 at 05:30:21PM +0300, Dmitry Gutov wrote:
>On 07.04.2022 14:48, Joel Reicher wrote:
>>It seems to me that, at least in the case of git, 'git grep' offers a superior implementation to anything offered by the generic implementation of project-find-regexp.
>
>Last I checked, there was no way to make 'git grep' search in 
>untracked files.
>
>That would be a violation of the contract.
>
>And of course we'd have to spend the effort to teach it about 
>user-customized error patterns.
>
>If 'git ls-files' + 'xargs rg' gives similar performance, that's 
>probably good enough. Though serializing the list of files back and 
>forth adds its overhead, which is unfortunate.
>
Just a question here.. why to use 'xargs rg'... AFAIK rg already perform
a parallel search..



  reply	other threads:[~2022-04-07 16:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 11:48 Should project delegate project-find-regexp? Joel Reicher
2022-04-07 12:34 ` Ergus
2022-04-07 12:55   ` Joel Reicher
2022-04-07 14:30 ` Dmitry Gutov
2022-04-07 16:10   ` Ergus [this message]
2022-04-07 16:33     ` Dmitry Gutov
2022-04-08  8:40   ` Joel Reicher
2022-04-18  3:01     ` Dmitry Gutov
2022-04-09 23:01   ` Jim Porter
2022-04-18  3:06     ` Dmitry Gutov
2022-04-07 16:56 ` Sean Whitton

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=20220407161015.bky7j2ljqj6ebgym@Ergus \
    --to=spacibba@aol.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=joel.reicher@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).