From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mattiase@acm.org, emacs-devel@gnu.org
Subject: Re: master 544db1e: Faster grep pattern for identifiers
Date: Wed, 15 Sep 2021 21:39:36 +0300 [thread overview]
Message-ID: <ee8b7d7f-abd1-42fc-a273-819ccef3c4e7@yandex.ru> (raw)
In-Reply-To: <8335q5bt9b.fsf@gnu.org>
On 15.09.2021 21:14, Eli Zaretskii wrote:
>> Cc:mattiase@acm.org,emacs-devel@gnu.org
>> From: Dmitry Gutov<dgutov@yandex.ru>
>> Date: Wed, 15 Sep 2021 21:06:09 +0300
>>
>> On 15.09.2021 19:33, Eli Zaretskii wrote:
>>> And what about the "alternative Grep's"?
>> The author of the commit uses one such Grep.
>>
>> I also tested with ripgrep, to similar success.
> So they all have, miraculously, the same notion of what is a word,
> regardless of the programming language and the script/character set?
> Amazing.
Not exactly (e.g. Grep includes international chars in the "word" set,
and Ripgrep does not), but the notions of "not word" are compatible
enough for our purposes.
Speaking of Ripgrep, the compatible behavior of -w is only with recent
versions (reported and fixed in
https://github.com/BurntSushi/ripgrep/issues/389), starting with 0.10.0.
Debian 10 and Fedora 31 include that versions or newer
(https://repology.org/project/ripgrep/versions).
Not that it's really important: we don't support Ripgrep officially.
next prev parent reply other threads:[~2021-09-15 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 15:56 master 544db1e: Faster grep pattern for identifiers Eli Zaretskii
2021-09-15 16:25 ` Dmitry Gutov
2021-09-15 16:33 ` Eli Zaretskii
2021-09-15 18:06 ` Dmitry Gutov
2021-09-15 18:14 ` Eli Zaretskii
2021-09-15 18:39 ` Dmitry Gutov [this message]
2021-09-17 16:07 ` bug#49836: Support ripgrep in semantic-symref-tool-grep Juri Linkov
2021-09-17 16:24 ` Lars Ingebrigtsen
2021-09-18 18:37 ` Juri Linkov
2021-09-16 7:28 ` master 544db1e: Faster grep pattern for identifiers Omar Polo
2021-09-15 16:29 ` Mattias Engdegård
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=ee8b7d7f-abd1-42fc-a273-819ccef3c4e7@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.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.