all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
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 18:14:15 +0300	[thread overview]
Message-ID: <83v8soai7s.fsf@gnu.org> (raw)
In-Reply-To: <87fsjs3j2y.fsf@gmail.com> (message from Visuwesh on Sat, 25 Jun 2022 20:07:25 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: tom@tromey.com,  28407@debbugs.gnu.org,  dgutov@yandex.ru
> Date: Sat, 25 Jun 2022 20:07:25 +0530
> 
> [சனி ஜூன் 25, 2022] Eli Zaretskii wrote:
> 
> > 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

That'd be against the purpose of TAGS tables: their explicit purpose
is to allow you to find definitions in _other_ files.  And Emacs
cannot know whether the fact that you loaded another TAGS table means
that you want to "forget" about the previous one, as long as you keep
it loaded.





      reply	other threads:[~2022-06-25 15:14 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
2022-06-25 15:14                   ` Eli Zaretskii [this message]

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=83v8soai7s.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28407@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=tom@tromey.com \
    --cc=visuweshm@gmail.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.