From: Patrick Mahan <plmahan@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Xref oddness
Date: Wed, 29 Apr 2020 12:00:27 -0700 [thread overview]
Message-ID: <CAFDHx1LX7m_9ZwKKmakdKMsrfnWBxewCbuEnMH=CaL7HXNQTHw@mail.gmail.com> (raw)
We have just recently upgraded some of our development machines to Ubuntu
18.04 which includes emacs 25.2 (we were on Ubuntu 16.04 and emacs 24.5).
I notice that emacs 25 brings with it changes to TAGS handling that have
been moved under Xref. But I am now seeing some odd behavior
Our sysadmins have setup where our home directories and development
directories are on multiple drives but are all symlinked through the same
top-level directory. For example, my actual home directory is on
/home2/patrick but it is access via /home/patrick (patrick under /home is
sym-linked to /home2/patrick). The same occurs for our development
directories (/development/patrick is sym-linked to /development5/patrick).
Now since our development directories are setup as multiple directories, I
was using the following method for finding TAGS files -
(setq tags-table-list (list "./" "../"
(concat (getenv "WORK") "/src/lib")
(concat (getenv "WORK") "/src/bin")
(concat (getenv "WORK") "/src/include")
(concat (getenv "WORK") "/src")))
WORK is defined as the top of my current development sandbox and changes as
I jump between sandboxes.
This worked great in 24.5, but now in 25.2 I am seeing multiple definitions
everytime I try to find a tag (M-.) (which is 'xref-find-definitions').
One for '/development5/..." and one for "/development/...".
Now that documentation mentions something about 'xref-etags-mode' as a
minor mode, but I cannot seem to invoke that mode in emacs. Is there a way
to fix this in Xref? Or should I just go back to redefining those keys to
the old 'find-tag' et.al.?
Thanks,
Patrick
next reply other threads:[~2020-04-29 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 19:00 Patrick Mahan [this message]
2020-04-29 19:20 ` Xref oddness Eli Zaretskii
2020-04-29 19:32 ` Patrick Mahan
2020-05-02 9:36 ` Eli Zaretskii
2020-05-06 23:17 ` Patrick Mahan
2020-05-19 15:13 ` Eli Zaretskii
2020-05-19 19:14 ` Patrick Mahan
2020-05-20 2:23 ` 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
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='CAFDHx1LX7m_9ZwKKmakdKMsrfnWBxewCbuEnMH=CaL7HXNQTHw@mail.gmail.com' \
--to=plmahan@gmail.com \
--cc=help-gnu-emacs@gnu.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.
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).