From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22947@debbugs.gnu.org, rogers@modulargenetics.com
Subject: bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags
Date: Thu, 10 Mar 2016 16:16:14 +0200 [thread overview]
Message-ID: <83twkel8pd.fsf@gnu.org> (raw)
In-Reply-To: <272376b7-ad78-a16d-ceeb-d7408fb59fdb@yandex.ru> (message from Dmitry Gutov on Thu, 10 Mar 2016 15:36:58 +0200)
> Cc: 22947@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 10 Mar 2016 15:36:58 +0200
>
> So we need to generate unqualified tag names, in addition to (or simply
> instead of) the qualified ones like the above.
So which one is better: both unqualified and qualified, or just
unqualified?
What symbol does xref pick up in a Perl buffer, when we have a
qualified name at point?
next prev parent reply other threads:[~2016-03-10 14:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 18:27 bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags Bob Rogers
2016-03-09 1:52 ` Dmitry Gutov
2016-03-09 2:43 ` Bob Rogers
2016-03-10 13:20 ` Eli Zaretskii
2016-03-10 13:36 ` Dmitry Gutov
2016-03-10 14:16 ` Eli Zaretskii [this message]
2016-03-10 14:34 ` Dmitry Gutov
2016-03-10 15:31 ` Eli Zaretskii
2016-03-10 15:50 ` Dmitry Gutov
2016-03-10 16:22 ` Eli Zaretskii
2016-03-11 1:45 ` Dmitry Gutov
2016-03-11 8:04 ` Eli Zaretskii
2016-03-11 12:46 ` Dmitry Gutov
2016-03-11 14:59 ` Eli Zaretskii
2016-03-12 1:08 ` Dmitry Gutov
2016-03-12 7:41 ` Eli Zaretskii
2016-03-12 12:10 ` Dmitry Gutov
2016-03-12 12:33 ` Eli Zaretskii
2016-03-12 12:46 ` Dmitry Gutov
2016-03-12 16:09 ` Eli Zaretskii
2016-03-10 19:07 ` Bob Rogers
2016-03-10 20:32 ` Eli Zaretskii
2016-03-11 18:08 ` Bob Rogers
2016-03-11 18:34 ` Eli Zaretskii
2016-03-11 19:05 ` Bob Rogers
2016-03-12 0:50 ` Dmitry Gutov
2022-04-26 12:40 ` Lars Ingebrigtsen
2022-04-26 17:00 ` Bob Rogers
2022-04-27 12:14 ` Lars Ingebrigtsen
2016-03-11 1:28 ` Dmitry Gutov
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=83twkel8pd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22947@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=rogers@modulargenetics.com \
/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).