From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43086@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#43086: [PATCH] Allow tags backend to not query for TAGS file
Date: Sun, 14 Nov 2021 00:02:08 +0000 [thread overview]
Message-ID: <87v90veha7.fsf@posteo.net> (raw)
In-Reply-To: <87r1blu6eu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 12 Nov 2021 09:25:45 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>>>> - 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.
>>> I'm ok with that, the variable could also be turned into a hook if
>>> reducing preconfigured options while making it easy to add new
>>> behaviours.
>>
>> Not sure how the direct conversion to a hook would look like.
>>
>> In any case, when I talked about using a hook (find-file-hook in
>> particular), the main benefit I had in mind is that the effect would
>> cover all uses of etags.el. Meaning, also
>> tags-completion-at-point-function.
>
> This was over a year ago, and it's unclear whether we wanted to do in
> Philip's patch's direction or not?
What exactly was the issue with my suggestion?
--
Philip Kaludercic
next prev parent reply other threads:[~2021-11-14 0:02 UTC|newest]
Thread overview: 18+ 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
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 [this message]
2022-09-11 11:36 ` Lars Ingebrigtsen
2022-09-13 4:07 ` Richard Stallman
2024-09-03 16:39 ` Philip Kaludercic
2024-09-06 22:16 ` Dmitry Gutov
2024-09-07 6:18 ` Eli Zaretskii
2024-09-09 0:29 ` Dmitry Gutov
2024-09-09 11:54 ` Eli Zaretskii
2024-09-09 23:32 ` Dmitry Gutov
2024-09-10 11:41 ` Eli Zaretskii
2024-09-10 12:45 ` Eli Zaretskii
2024-09-10 13:32 ` Dmitry Gutov
2024-09-10 13:30 ` Dmitry Gutov
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=87v90veha7.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=43086@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.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 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).