hasktags - etags backend, any reason to not remove function arguments from tag files?
Hi list, hasktags -e generates lines containing the function arguments. For Example: f0 foo\x7f5,6 The "foo" is the function arg, not the keyword to be tagged. Emacs still finds f0, but it does not show it in tab completion using m-x find-tag .. I don't use Emacs myself. That's why I want to ask whether this is intention or a bug. The fix is trivial: use "name" of FoundThing instead of "concat (take (token + 1) $ spacedwords fullline)" Is there any reason to keep current behaviour? Marc Weber
Marc Weber
hasktags -e generates lines containing the function arguments. For Example:
f0 foo\x7f5,6
The "foo" is the function arg, not the keyword to be tagged.
I've given the issue a bit more thought based on the wikipedia description[1], according to which format an etag line should have is: | {tag_definition_text}<\x7f>{tagname}<\x01>{line_number},{byte_offset} | | {tagname} (along with \x01) can be omitted if the name of the tag can | be deduced from the text at the tag definition. ...the problem here seems that Emacs can't deduce the tagname from the definition text, thus the "{tagname}<\x01>" part should be explicitly generated by hasktags IMHO I guess (= I haven't checked the actual elisp code) that '{tag_definition_text}' is useful for Emacs to help compensate for changed line-numbers since etags-generation-time, when locating the original definition-line... [1]: http://en.wikipedia.org/wiki/Ctags#Etags_2 --
Excerpts from Herbert Valerio Riedel's message of Tue Mar 20 15:38:54 +0100 2012:
[1]: http://en.wikipedia.org/wiki/Ctags#Etags_2 \0x7f and \0x1
record and pushed this fix. Marc Weber
participants (2)
-
Herbert Valerio Riedel -
Marc Weber