From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
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:34:02 +0200 [thread overview]
Message-ID: <1a1318bc-f092-ab68-197f-91d5e11bb821@yandex.ru> (raw)
In-Reply-To: <83twkel8pd.fsf@gnu.org>
On 03/10/2016 04:16 PM, Eli Zaretskii wrote:
> So which one is better: both unqualified and qualified, or just
> unqualified?
We've had this discussion before: including the qualified names
increases the size of the table, but allows the user to pick the
qualified name if they don't mind typing it in the prompt, with completion.
It's a tradeoff. "No qualified names" is probably a better default,
because the user needs extra knowledge to make use of them. So they
might as well have to find out how to turn them on.
> What symbol does xref pick up in a Perl buffer, when we have a
> qualified name at point?
Like in other languages, the unqualified one (most of the time).
next prev parent reply other threads:[~2016-03-10 14:34 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
2016-03-10 14:34 ` Dmitry Gutov [this message]
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=1a1318bc-f092-ab68-197f-91d5e11bb821@yandex.ru \
--to=dgutov@yandex.ru \
--cc=22947@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).