From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tom@tromey.com, 28407@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#28407: 26.0.50; xref should use imenu
Date: Sat, 25 Jun 2022 20:07:25 +0530 [thread overview]
Message-ID: <87fsjs3j2y.fsf@gmail.com> (raw)
In-Reply-To: <83wnd4akqa.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Jun 2022 17:19:57 +0300")
[சனி ஜூன் 25, 2022] Eli Zaretskii wrote:
>> Cc: Tom Tromey <tom@tromey.com>, 28407@debbugs.gnu.org
>> From: Visuwesh <visuweshm@gmail.com>
>> Date: Sat, 25 Jun 2022 19:34:48 +0530
>>
>> [ To elaborate, say that I visited the TAGS residing in Emacs' src/
>> directory then switched to another project. Now, if I do C-u
>> M-. Fplist_get RET, then it will take me to the Emacs project!! This
>> seems to be a general problem with the etags backend tho. ]
>
> In general, when you visit a new TAGS file, etags asks you whether to
> replace the previous one or to keep them both. Maybe the way you
> "switch to another project" somehow hides that prompt/decision?
It does ask me to replace the previous one but I expected Emacs to
restrict the TAGS file to the buffer I selected it from, mostly because
I was mislead to believe the check (or tags-table-files tags-file-name)
would work that way.
[ The check is from a previous revision of my patch. ]
next prev parent reply other threads:[~2022-06-25 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 16:23 bug#28407: 26.0.50; xref should use imenu Tom Tromey
2017-09-10 21:35 ` Dmitry Gutov
2022-05-15 12:32 ` Visuwesh
2022-05-16 6:59 ` Visuwesh
2022-05-29 22:13 ` Dmitry Gutov
2022-05-30 4:18 ` Visuwesh
2022-06-04 0:56 ` Dmitry Gutov
2022-06-25 14:04 ` Visuwesh
2022-06-25 14:19 ` Eli Zaretskii
2022-06-25 14:37 ` Visuwesh [this message]
2022-06-25 15:14 ` 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=87fsjs3j2y.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=28407@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=tom@tromey.com \
/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.