unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Patrick Mahan <plmahan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Xref oddness
Date: Wed, 6 May 2020 16:17:37 -0700	[thread overview]
Message-ID: <CAFDHx1LLwVAHGRMmrP9puk84LhUHjt0Gu1DKJg7hqN+X2eiVhA@mail.gmail.com> (raw)
In-Reply-To: <83o8r6u19a.fsf@gnu.org>

On Sat, May 2, 2020 at 2:39 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Patrick Mahan <plmahan@gmail.com>
> > Date: Wed, 29 Apr 2020 12:32:30 -0700
> > Cc: help-gnu-emacs@gnu.org
> >
> > I realized I forgot to describe the problem I am seeing.  If I am
> editing a file in a sandbox, for example, emacs
> > $WORK/src/bin/app1/main.c, then need to find a tag (M-.) under 25.2 it
> always gives me two choices, both
> > are same, except one shows the sym-linked directory and the other shows
> the realpath directory.  Forcing
> > me to have to chose.
>
> What do you see in the TAGS file in this case?  Are there 2 entries
> there for each function/variable, one for the real directory and
> another for the symlink, or is there only one entry?
>
>
Sorry, IRL is intruding here.

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.

If I override these settings back to the original 'find-tag' and
'find-tag-other-window' it works as expected.

Patrick


  reply	other threads:[~2020-05-06 23:17 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 [this message]
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=CAFDHx1LLwVAHGRMmrP9puk84LhUHjt0Gu1DKJg7hqN+X2eiVhA@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).