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
On 05/26/2015 10:23 PM, Eli Zaretskii wrote:
> I don't see how that could be possible: tag-implicit-name-match-p is
> language-agnostic. You'd need to make it language-aware before it
> could do such stuff for languages that need it.
Well, by including ()=,; in that constant, it already makes certain
assumptions that aren't necessarily true (for instance, `=' can be, and
often is, a part of a method name in Ruby). Adding a colon would be
another one of those.
Not that I necessarily advocate for it, mind you.
> It slips my mind for a moment, but there's some command whose
> completion shows <f> for functions, <v> for variables, etc.
elisp-completion-at-point can do that.
> And it's not the only one, I'm quite sure I saw longer text after each
> candidate, perhaps somewhere in 'company'?
That's possible. But either way, these are annotations for existing
completions. What the suggested patch would do, though, is add new
completions.
> What kind of junk?
Among patterns for tags with explicit names, there could be some odd
ones. We never showed them before, I think, anywhere.
You should try the patch and see how it goes.
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.