From: Dmitry Gutov <dgutov@yandex.ru>
To: "Philip K." <philipk@posteo.net>, 43086@debbugs.gnu.org
Subject: bug#43086: [PATCH] Allow tags backend to not query for TAGS file
Date: Sat, 5 Sep 2020 03:45:17 +0300 [thread overview]
Message-ID: <cfd9096b-6787-236e-7780-df2aa63a94d3@yandex.ru> (raw)
In-Reply-To: <87k0xjue75.fsf@posteo.net>
Hi!
On 28.08.2020 15:50, Philip K. wrote:
> the xref backend for etags can be annoying at times, especially in
> combination with other backends. This patch should improve the
> situation, by allowing the user to configure how and when the etags
> backend is activated. The new user option etags-query-file would allow
> the backend to never query a TAGS file, or conditionally, depending on
> the existence of a TAGS file (in which case it can also be automatically
> loaded).
This is a interesting patch, but it calls for some discussion:
- The possible values all look pretty clever, but there are a lot of
them! Do we expect them all to be in demand? Ideally, I'd only leave 2-3
of them, to reduce the number of workflows we need to care about. The
rest could probably be set up in individual user configurations in
find-file-hook (like Projectile does).
- The variable name implies it affects how etags.el works globally, but
the actual effect seems limited to the xref backend function. We should
either rename it to something like etags-xref-query-file, or consider
having it affect tags-completion-at-point-function as well. Maybe
find-tag too. But given that tags-completion-at-point-function has for a
long time behaved in the "never query" fashion, perhaps the easiest and
most backward-compatible option is the former.
- One current persistent annoyance is that currently
xref-find-references doesn't work well in many files where the xref
backend is the default one (etags) when ido-mode or icomplete-mode are
enabled because it prompts for the tags file to do identifier
completion. I wonder if the "no query" option will help with this, too.
> I could imagine this might be extended to allow an auto-generate option,
> but that feature seems out of scope of this patch, and probably would
> require some interoperation with project.el.
Indeed. Actually, I have an old, WIP patch for tag file auto-generation
which, yes, uses project.el. I can post it again if you're curious.
next prev parent reply other threads:[~2020-09-05 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 12:50 bug#43086: [PATCH] Allow tags backend to not query for TAGS file Philip K.
2020-09-05 0:45 ` Dmitry Gutov [this message]
2020-09-06 21:50 ` Philip K.
2020-09-16 10:53 ` Dmitry Gutov
2021-11-12 8:25 ` Lars Ingebrigtsen
2021-11-14 0:02 ` Philip Kaludercic
2022-09-11 11:36 ` Lars Ingebrigtsen
2022-09-13 4:07 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfd9096b-6787-236e-7780-df2aa63a94d3@yandex.ru \
--to=dgutov@yandex.ru \
--cc=43086@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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.