From: Patrick Mahan <plmahan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Xref oddness
Date: Tue, 19 May 2020 12:14:14 -0700 [thread overview]
Message-ID: <CAFDHx1LXz08OFgRYU2XhXjSXYmi9s3Hx2TBsbjyWCydY-0bRtA@mail.gmail.com> (raw)
In-Reply-To: <831rng7ya1.fsf@gnu.org>
On Tue, May 19, 2020 at 8:37 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Patrick Mahan <plmahan@gmail.com>
> > Date: Wed, 6 May 2020 16:17:37 -0700
> > Cc: help-gnu-emacs@gnu.org
> >
> > Sorry, IRL is intruding here.
>
> Here as well.
>
> > In all TAGS files I only see 1 entry for the tag and the file is shown
> as /home/pmahan/... not /home2/pmahan.
> >
> > But again, when I attempt to xref-find-tag-other-window, it is giving me
> two options to choose from and then
> > it bounces back to the original window and displays the output there
> instead of just using the new window (or
> > creating a new window). This is becoming annoying because it is
> breaking finding a tag that exists inside the
> > current source file.
>
> I looked at the relevant code, and couldn't spot where we could make
> two tags out of just one due to your use of symlinks. So I suspect
> there's some other factor at work here. I therefore suggest that you
> submit a bug report, using "M-x report-emacs-bug RET", with all the
> details, and preferably also a small test case that could be used to
> reproduce the problem. Then we could use those details to debug this
> more thoroughly.
>
>
Thanks, I will do so. Though I believe the hint is due to the symlinked
directory. Is there anything doing something similar to 'readlink'?
Thanks,
Patrick
next prev parent reply other threads:[~2020-05-19 19:14 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
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 [this message]
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=CAFDHx1LXz08OFgRYU2XhXjSXYmi9s3Hx2TBsbjyWCydY-0bRtA@mail.gmail.com \
--to=plmahan@gmail.com \
--cc=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).