From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Xref oddness
Date: Wed, 29 Apr 2020 22:20:59 +0300 [thread overview]
Message-ID: <83blnaxfms.fsf@gnu.org> (raw)
In-Reply-To: <CAFDHx1LX7m_9ZwKKmakdKMsrfnWBxewCbuEnMH=CaL7HXNQTHw@mail.gmail.com> (message from Patrick Mahan on Wed, 29 Apr 2020 12:00:27 -0700)
> From: Patrick Mahan <plmahan@gmail.com>
> Date: Wed, 29 Apr 2020 12:00:27 -0700
>
> 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.
I don't think I understand how the symlinks come into play here.
Could you please tell more? How do you get from $WORK to
/home/patrick and /home2/patrick? or maybe its /development/patrick
and /development5/patrick? I'm confused.
> Or should I just go back to redefining those keys to the old
> 'find-tag' et.al.?
Not recommended: you'll be fighting an uphill battle. Perhaps there's
a bug, or there's a way to configure your Emacs a bit differently.
next prev parent reply other threads:[~2020-04-29 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 19:00 Xref oddness Patrick Mahan
2020-04-29 19:20 ` Eli Zaretskii [this message]
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=83blnaxfms.fsf@gnu.org \
--to=eliz@gnu.org \
--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).