all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Patrick Mahan <plmahan@gmail.com>
To: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Using xref-find-definitions
Date: Fri, 6 Oct 2023 11:38:18 -0700	[thread overview]
Message-ID: <CAFDHx1KyipKugLKcSCR4bSXqJJu4znabM-XE1WeWLJ_Oo=Z4Fg@mail.gmail.com> (raw)

I am running 25.2.2 on Ubuntu 18.04 release.

I am working on a large software project, with lots of subdirectories and
lots of files.  Originally, TAGS are built using the cascading makefiles
(one per directory) so you get a TAGS file in each directory and as you
move up the TAGS file also incorporates the ones below it (without the use
of the --include command).  In my emacs init file I have tags-table-list
set to the list of locations for the tag 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"))))

This has worked well for a while now using the older find-tags command.
But now that command is no longer supported and I need to use
xref-find-definitions.  Which works fine, for the most part, but
occasionally I run across the following issue -

An *xref* buffer appears with the following -
/home/pmahan/workspaces/myos/src/bin/mserv/appclass/my_ipserv.c
109: void flow_log(
/home/pmahan/workspaces/myos/src/bin/mserv/appclass/my_ipserv.c
109: void flow_log(

When I was using find-tag, it would give me the first hit, then I could do
CTRL-u M-. to go to the next entry.  I would not have this presented.  In
the new method, this is churning my buffer displays around which is
annoying, especially when the entry is in the same code module.

My current assumption is that this is due to all of the various TAGS files
that have duplicate entries.  Is it time to change how we generate TAGS?
Or can I configure xref-find-definitions to handle this situation.

Thanks,

Patrick


             reply	other threads:[~2023-10-06 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 18:38 Patrick Mahan [this message]
2023-10-07  6:02 ` Using xref-find-definitions Eli Zaretskii
2023-10-07  7:35   ` Patrick Mahan
2023-10-07 19:05     ` Patrick Mahan

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='CAFDHx1KyipKugLKcSCR4bSXqJJu4znabM-XE1WeWLJ_Oo=Z4Fg@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.
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.