From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28409-done@debbugs.gnu.org, Tom Tromey <tom@tromey.com>
Subject: bug#28409: 26.0.50; xref, tags, and multiple projects
Date: Mon, 10 Aug 2020 09:47:25 -0700 [thread overview]
Message-ID: <CADwFkmmu8B9y5begZojZrLXtyOXbVWJz7ou3_aEf7-9_WC9PKg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnXL72L+5iFte7JotARFOFaucFJBkPovauTQTgZjc=rAg@mail.gmail.com> (Stefan Kangas's message of "Sun, 29 Sep 2019 03:18:42 +0200")
Stefan Kangas <stefan@marxist.se> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Tom Tromey <tom@tromey.com>
>>> Date: Sun, 10 Sep 2017 12:29:03 -0600
>>>
>>> I have multiple projects open at a given time.
>>>
>>> If I use xref on two projects, and load tags file for both, I would like
>>> it if the tags were project-specific. Currently I only have the option
>>> to keep all the tags files together, which sometimes leads to conflicts
>>> where the same symbol appears in both projects.
>>
>> You should be able to make the tags tables local to a buffer by
>> invoking visit-tags-table with a prefix argument (see the doc string
>> of that command for details). Did you try that?
>
> Hi Tom,
>
> Did the above solve the issue for you?
>
> Best regards,
> Stefan Kangas
More information was requested, but none was given within 45 weeks, so
I'm closing this bug. If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-08-10 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 18:29 bug#28409: 26.0.50; xref, tags, and multiple projects Tom Tromey
2017-09-10 19:40 ` Eli Zaretskii
2019-09-29 1:18 ` Stefan Kangas
2020-08-10 16:47 ` Stefan Kangas [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=CADwFkmmu8B9y5begZojZrLXtyOXbVWJz7ou3_aEf7-9_WC9PKg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=28409-done@debbugs.gnu.org \
--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.