unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, Dmitry Gutov <dgutov@yandex.ru>
Cc: matzikratzi@gmail.com, 2544@debbugs.gnu.org
Subject: bug#2544: 23.0.60; Could etags please try find a local tag first?
Date: Mon, 19 Jul 2021 18:56:22 +0300	[thread overview]
Message-ID: <8335sa70wp.fsf@gnu.org> (raw)
In-Reply-To: <878s22nyuj.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  19 Jul 2021 16:48:52 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 19 Jul 2021 16:48:52 +0200
> Cc: 2544@debbugs.gnu.org
> 
> Matzi Kratzi <matzikratzi@gmail.com> writes:
> 
> > Would it make sense, in general, for etags to first try to find a tag
> > inside the current buffer? I am working in legacy code that has the
> > same name for certain help functions in many files. I would like etags
> > to first try find the tag inside the current buffer.
> 
> (I'm going through old bug reports that unfortunately got no response at
> the time.)
> 
> I can certainly see cases where that would be useful.  I think much of
> this stuff has been rewritten in terms of xref now?  I gave the xref
> code a quick look-over, but I didn't see anything obvious in this
> area...
> 
> Does anybody know whether Emacs grown support for this use case in the
> 12 years since this bug report was filed?

We did switch to Xref, but for many languages (including C), Xref
still uses etags as its back-end.  So etags is still relevant.

As for the original request: I guess we could satisfy that by having
Xref sort the matches so that those in the current buffer come first
in the display we show in the *XREF* buffer?  Dmitry, would it make
sense to add such an option, and if so, would it be hard to do so?  In
xref--alistify, perhaps, or in xref--analyze?





  reply	other threads:[~2021-07-19 15:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 21:36 bug#2544: 23.0.60; Could etags please try find a local tag first? Matzi Kratzi
2021-07-19 14:48 ` Lars Ingebrigtsen
2021-07-19 15:56   ` Eli Zaretskii [this message]
2021-07-19 23:00     ` Dmitry Gutov
2021-07-20 11:51       ` Lars Ingebrigtsen
2021-07-20 16:15         ` Dmitry Gutov
2021-07-20 11:54       ` Eli Zaretskii
2021-07-20 16:22         ` Dmitry Gutov
2021-07-20 16:56           ` Eli Zaretskii
2021-07-20 22:36             ` Dmitry Gutov
2021-07-21 10:39               ` Lars Ingebrigtsen
2021-07-26 23:15                 ` Dmitry Gutov
2021-07-28 15:49                   ` Lars Ingebrigtsen
2021-08-02  2:11                     ` Dmitry Gutov
2021-08-02 11:36                       ` Eli Zaretskii
2021-08-06  0:17                         ` Dmitry Gutov

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=8335sa70wp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=2544@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=larsi@gnus.org \
    --cc=matzikratzi@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).