unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: larsi@gnus.org, matzikratzi@gmail.com, 2544@debbugs.gnu.org
Subject: bug#2544: 23.0.60; Could etags please try find a local tag first?
Date: Tue, 20 Jul 2021 14:54:39 +0300	[thread overview]
Message-ID: <83lf615hfk.fsf@gnu.org> (raw)
In-Reply-To: <417d5d01-c3a9-a75e-b134-7f1847749842@yandex.ru> (message from Dmitry Gutov on Tue, 20 Jul 2021 02:00:31 +0300)

> Cc: matzikratzi@gmail.com, 2544@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 20 Jul 2021 02:00:31 +0300
> 
> On 19.07.2021 18:56, Eli Zaretskii wrote:
> > 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?
> 
> It would probably better work as an etags option (residing next to 
> etags-xref-find-definitions-tag-order): Xref, in general, cannot know in 
> advance whether a given tags resides in the current buffer, and 
> following all tags is relatively costly.

But then this feature will be reserved only for the etags backend, no?

Maybe there should be a backend-specific sorting method or something?

> I was thinking to suggest having that behavior on by default (and maybe 
> avoid adding a new variable altogether), but it seems to conflict with 
> the intention behind etags-xref-find-definitions-tag-order, so probably not.

Right.





  parent reply	other threads:[~2021-07-20 11:54 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
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 [this message]
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=83lf615hfk.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).