From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: gregory@heytings.org, 50733@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#50733: 28.0.1; project-find-regexp can block Emacs for a long time
Date: Fri, 24 Sep 2021 21:51:58 +0300 [thread overview]
Message-ID: <83fsttst69.fsf@gnu.org> (raw)
In-Reply-To: <843b49c3-08e1-239f-d6bc-850cc2d78ca1@yandex.ru> (message from Dmitry Gutov on Fri, 24 Sep 2021 21:17:24 +0300)
> Cc: 50733@debbugs.gnu.org, mardani29@yahoo.es
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 24 Sep 2021 21:17:24 +0300
>
> On 24.09.2021 20:49, Eli Zaretskii wrote:
> > Hint: they are all in comments.
>
> It's not an obvious choice, BTW: whether to show references to the
> identifier in comments.
>
> Personally, I think I prefer the current behavior of
> xref-find-references when using Grep for searching.
I won't argue about personal preferences. IMO, it isn't a matter of
preference, it's a matter of matching between a job you have to do and
the best tool for that job.
> Because, when you are renaming a function, you don't want to forget the
> references to its name in comments across the project.
Renaming identifiers is not the only job that needs these outputs.
next prev parent reply other threads:[~2021-09-24 18:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1h7edq7sc.fsf.ref@yahoo.es>
2021-09-22 9:27 ` bug#50733: 28.0.1; project-find-regexp can block Emacs for a long time Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-22 19:09 ` Dmitry Gutov
2021-09-22 21:58 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-22 23:09 ` Dmitry Gutov
2021-09-23 17:41 ` Dmitry Gutov
2021-09-23 21:17 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-23 22:40 ` Dmitry Gutov
2021-09-24 6:34 ` Eli Zaretskii
2021-09-24 7:02 ` Juri Linkov
2021-09-24 10:43 ` Eli Zaretskii
2021-09-24 15:30 ` Juri Linkov
2021-09-24 16:08 ` Eli Zaretskii
2021-09-24 9:00 ` Gregory Heytings
2021-09-24 11:00 ` Eli Zaretskii
2021-09-24 11:43 ` Dmitry Gutov
2021-09-24 13:18 ` Gregory Heytings
2021-09-24 14:20 ` Eli Zaretskii
2021-09-24 15:50 ` Dmitry Gutov
2021-09-24 16:18 ` Eli Zaretskii
2021-09-24 16:22 ` Dmitry Gutov
2021-09-24 16:24 ` Gregory Heytings
2021-09-24 17:49 ` Eli Zaretskii
2021-09-24 17:52 ` Gregory Heytings
2021-09-24 18:48 ` Eli Zaretskii
2021-09-24 21:49 ` Gregory Heytings
2021-09-25 6:26 ` Eli Zaretskii
2021-09-27 0:43 ` Gregory Heytings
2021-09-27 5:14 ` Eli Zaretskii
2021-09-27 9:23 ` Gregory Heytings
2021-09-27 11:48 ` Eli Zaretskii
2021-09-27 12:25 ` Gregory Heytings
2021-09-27 12:44 ` Eli Zaretskii
2021-09-27 19:36 ` Gregory Heytings
2021-09-28 5:17 ` Eli Zaretskii
2021-09-28 8:23 ` Gregory Heytings
2021-09-27 12:58 ` Dmitry Gutov
2021-09-27 13:05 ` Eli Zaretskii
2021-09-27 19:37 ` Gregory Heytings
2021-09-24 18:17 ` Dmitry Gutov
2021-09-24 18:51 ` Eli Zaretskii [this message]
2021-09-24 11:40 ` Dmitry Gutov
2021-09-24 12:02 ` Eli Zaretskii
2021-09-24 12:22 ` Dmitry Gutov
2021-09-24 13:06 ` Eli Zaretskii
2021-09-24 14:05 ` Dmitry Gutov
2021-09-23 6:13 ` Eli Zaretskii
2021-09-23 20:42 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-23 22:18 ` Dmitry Gutov
2021-09-24 6:03 ` Eli Zaretskii
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=83fsttst69.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50733@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=gregory@heytings.org \
--cc=mardani29@yahoo.es \
/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.