bug#21934: 24.5; find-tag: reading TAGS file incorrectly

[Andreas Matthias]

Eli Zaretskii wrote:

>> From: Andreas Matthias <andreas.matthias@gmail.com>
>> Cc: dgutov@yandex.ru,  21934@debbugs.gnu.org
>> Date: Mon, 23 Nov 2015 17:50:40 +0100
>> 
>> Eli Zaretskii wrote:
>> 
>> >> From: Andreas Matthias <andreas.matthias@gmail.com>
>> >> Cc: Eli Zaretskii <eliz@gnu.org>,  21934@debbugs.gnu.org
>> >> Date: Sun, 22 Nov 2015 18:49:32 +0100
>> >> 
>> >> >> Can there be
>> >> >> more than one of these in a token, and if so, what should etags do?
>> >> >> IOW, if we have foo.bar.baz or foo:bar.baz etc., what should be the
>> >> >> result?
>> >> >
>> >> > Just two, I think. foo.bar is not a function, and bar.baz probably 
>> >> > won't be a
>> >> > "symbol at point".
>> >> >
>> >> > So just the fully qualified tag name, and the local tag name ("baz").
>> >> 
>> >> Yes, that's reasonable.
>> >
>> > I'm sorry: can I have a complete specification, please?  Given a
>> > token that includes one or more of '.' and ':', how to determine the 2
>> > tags that etags should produce?
>> 
>> See `funcname' in:
>> 
>> http://www.lua.org/manual/5.3/manual.html#9
>
> Thanks, but that's not all the information I need.  What's missing is
> which part(s) of a funcname would you like etags to record.  Do you
> want each "Name" component to be recorded, or just some of them?
>
> IOW, if we have foo.bar.baz.more, what should be recorded in addition
> to the whole foo.bar.baz.more token?  Just bar.baz.more, or something
> else?  What about foo.bar.baz:more?

As Dmitry said. Both the fully qualified tag name and the local tag name.


foo.bar.baz.more should be tagged as:

   foo.bar.baz.more
   more


foo.bar.baz:more should be tagged as:

   foo.bar.baz:more
   more