GNU bug report logs -
#20629
25.0.50; Regression: TAGS broken, can't find anything in C++ files.
Previous Next
Reported by: "Jan D." <jan.h.d <at> swipnet.se>
Date: Fri, 22 May 2015 05:59:02 UTC
Severity: normal
Found in version 25.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Cc: 20629 <at> debbugs.gnu.org
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> Date: Sat, 30 May 2015 01:36:56 +0300
>
> On 05/29/2015 11:35 PM, Eli Zaretskii wrote:
>
> > xref expects more accurate results, because it shows them all at once,
> > instead of one by one, in some order that assures the users will only
> > ever see the few first ones. So yes, I'd say the switch to xref puts
> > a different kind of pressure on what etags/ctags does.
>
> It does exert some pressure, but mostly to ensure that when a user
> searches for a "symbol" that they see in a buffer, it should have an
> explicit or an implicit tag match.
The crucial difference is that the number of matches must now be
small, something that required us to remove the method which could
cope with qualified tags when the symbol at point was unqualified.
> Whether qualified tag names are included in the completion, and whether
> one can search for a qualified tag name reliably, that hasn't changed
> between find-tag and xref-find-definitions.
True. But the original arrangement worked well with both with
find-tag and with completions; now that we removed tag-symbol-match-p
and qualified names, completion is less user-friendly.
So I think we should default to having 2 entries for each such tag.
This bug report was last modified 9 years and 69 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.