From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Matthias <andreas.matthias@gmail.com>
Cc: 21934@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#21934: 24.5; find-tag: reading TAGS file incorrectly
Date: Sun, 22 Nov 2015 20:13:25 +0200 [thread overview]
Message-ID: <83bnal3nsq.fsf@gnu.org> (raw)
In-Reply-To: <877fl9sz4j.fsf@winky.hogwarts>
> 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?
TIA
next prev parent reply other threads:[~2015-11-22 18:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 19:47 bug#21934: 24.5; find-tag: reading TAGS file incorrectly Andreas Matthias
2015-11-17 4:01 ` Dmitry Gutov
2015-11-17 16:06 ` Eli Zaretskii
2015-11-17 17:21 ` Andreas Matthias
2015-11-17 17:24 ` Dmitry Gutov
2015-11-17 17:40 ` Andreas Matthias
2015-11-17 17:46 ` Dmitry Gutov
2015-11-17 19:38 ` Andreas Matthias
2015-11-18 1:56 ` Dmitry Gutov
2015-11-21 13:07 ` Eli Zaretskii
2015-11-22 1:17 ` Dmitry Gutov
2015-11-22 4:38 ` Dmitry Gutov
2015-11-22 14:08 ` Andreas Matthias
2015-11-22 14:33 ` Dmitry Gutov
2015-11-22 14:41 ` Dmitry Gutov
2015-11-22 15:06 ` Andreas Matthias
2015-11-22 15:23 ` Dmitry Gutov
2015-11-22 16:41 ` Andreas Matthias
2015-11-22 16:43 ` Dmitry Gutov
2015-11-22 16:12 ` Eli Zaretskii
2015-11-22 16:54 ` Dmitry Gutov
2015-11-22 17:38 ` Eli Zaretskii
2015-11-22 17:43 ` Dmitry Gutov
2015-11-22 17:49 ` Andreas Matthias
2015-11-22 18:13 ` Eli Zaretskii [this message]
2015-11-23 16:50 ` Andreas Matthias
2015-11-23 17:16 ` Eli Zaretskii
2015-11-23 17:28 ` Andreas Matthias
2015-11-23 18:17 ` Eli Zaretskii
2015-11-28 10:33 ` Eli Zaretskii
2015-11-28 17:25 ` Andreas Matthias
2015-11-30 17:34 ` Eli Zaretskii
2015-11-28 17:25 ` Andreas Matthias
2015-11-22 18:09 ` Eli Zaretskii
2015-11-22 18:27 ` Andreas Matthias
2015-11-22 18:33 ` Dmitry Gutov
2015-11-22 18:52 ` Andreas Matthias
2015-11-26 2:41 ` Dmitry Gutov
2015-11-17 11:05 ` Stephen Leake
2015-11-17 17:17 ` Andreas Matthias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bnal3nsq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21934@debbugs.gnu.org \
--cc=andreas.matthias@gmail.com \
--cc=dgutov@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).