GNU bug report logs - #2544
23.0.60; Could etags please try find a local tag first?

Previous Next

Package: emacs;

Reported by: Matzi Kratzi <matzikratzi <at> gmail.com>

Date: Mon, 2 Mar 2009 21:45:03 UTC

Severity: wishlist

Done: Dmitry Gutov <dgutov <at> yandex.ru>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: larsi <at> gnus.org, matzikratzi <at> gmail.com, 2544 <at> debbugs.gnu.org
Subject: bug#2544: 23.0.60; Could etags please try find a local tag first?
Date: Tue, 20 Jul 2021 19:56:53 +0300
> Cc: larsi <at> gnus.org, matzikratzi <at> gmail.com, 2544 <at> debbugs.gnu.org
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> Date: Tue, 20 Jul 2021 19:22:41 +0300
> 
> > But then this feature will be reserved only for the etags backend, no?
> > 
> > Maybe there should be a backend-specific sorting method or something?
> 
> Not 100% sure how that could work, but I'm reasonably certain that 
> "prioritize hits in the current file" is mostly relevant to etags.
> 
> Because when one uses more precise backends, "find definition" gets 
> fewer hits, and you don't really need to choose which ones to start with 
> -- the current file or otherwise.

When a backend returns just one hit, this is a non-issue.  The OP
specifically described a situation where there are many functions with
the same name in the project.  That's the use case we are discussing.
I don't see how the backend can affect this situation.  Especially
since the etags backend is also quite accurate.

But I'm going to stop arguing.  If there isn't enough enthusiasm for
implementing this, it will remain a pipe dream, I guess.




This bug report was last modified 3 years and 288 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.