From: Tom Tromey <tom@tromey.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Tom Tromey <tom@tromey.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: vc-git-grep vs project-find-regexp: Was: Re: bug#27840: 26.0.50; vc-git-grep stopped working on git master
Date: Sat, 29 Jul 2017 16:58:59 -0600 [thread overview]
Message-ID: <87iniaalzg.fsf@tromey.com> (raw)
In-Reply-To: <30c0c165-abc0-826d-8cf9-9646086c4648@yandex.ru> (Dmitry Gutov's message of "Thu, 27 Jul 2017 16:26:06 +0300")
>>>>> "Dmitry" == Dmitry Gutov <dgutov@yandex.ru> writes:
Dmitry> On 7/26/17 8:57 PM, Tom Tromey wrote:
>>
>> I am running a build of git master from yesterday.
>> I tried M-x vc-git-grep.
Dmitry> As an aside, have you tried M-x project-find-regexp? Any particular
Dmitry> dislikes?
Ok, I tried project-find-regexp and project-find-file yesterday.
The main issue is that they are just too slow.
I'm mostly developing Firefox these days, which has a very large source
tree.
For project-find-file, I somewhat expected it to be slow, but I was
surprised that project-find-regexp also appeared to just hang ... I
interrupted it before it did anything. Maybe it's also trying to
construct a file list? (I didn't check.) Would it be possible to cache
the file list and maybe watch the filesystem for additions?
I will try project-find-file some more and see if I have any quibbles
with it.
These would both be very nice to have...
thanks,
Tom
prev parent reply other threads:[~2017-07-29 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 17:57 bug#27840: 26.0.50; vc-git-grep stopped working on git master Tom Tromey
2017-07-26 23:32 ` npostavs
2017-07-27 13:23 ` Dmitry Gutov
2017-07-30 18:08 ` npostavs
2017-08-01 13:36 ` Dmitry Gutov
2017-08-03 3:09 ` npostavs
2017-08-04 0:59 ` Dmitry Gutov
2017-08-04 22:31 ` npostavs
2017-08-07 0:39 ` npostavs
2017-07-27 13:26 ` vc-git-grep vs project-find-regexp: Was: " Dmitry Gutov
2017-07-27 22:05 ` Tom Tromey
2017-07-29 22:58 ` Tom Tromey [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iniaalzg.fsf@tromey.com \
--to=tom@tromey.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@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.