From: Mike Kupfer <m.kupfer@acm.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22692@debbugs.gnu.org
Subject: bug#22692: 25.0.91; xref-find-definitions fails to prompt
Date: Tue, 16 Feb 2016 17:55:28 -0800 [thread overview]
Message-ID: <23698.1455674128@allegro.localdomain> (raw)
In-Reply-To: Your message of "Tue\, 16 Feb 2016 12\:12\:55 +0200." <56C2F627.6070308@yandex.ru>
Dmitry Gutov wrote:
> On 02/16/2016 03:02 AM, Mike Kupfer wrote:
> > If point is on a token that isn't defined in the current tags file,
> > M-. gives me an error (look for "Cygwin" further down in this bug
> > report). I expect to get a prompt.
>
> That doesn't sound right to me: "XXX is not found" is a valid piece of
> information. Simply showing a prompt would obscure it.
The Help string for xref-find-definitions says
> With prefix argument or when there’s no identifier at point,
> prompt for it.
I guess you could argue that if point is on a token that's not in the
tags table, it's still on an "identifier". But "#" is hardly an
identifier.
And the Info page "Xref Commands" says
> With a prefix argument, or if there’s no valid
> identifier at point, it prompts for the identifier.
Does "valid identifier" mean syntatically correct, or does it mean that
the identifier is in the tags table. Please clarify the documentation.
> If we accept that the command searches for the thing at point by
> default, the current behavior seems appropriate. And whether or not it
> prompts, is customizable.
Yes, I have already have
(setq xref-prompt-for-identifier t)
in my .emacs.
mike
next prev parent reply other threads:[~2016-02-17 1:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 1:02 bug#22692: 25.0.91; xref-find-definitions fails to prompt Mike Kupfer
2016-02-16 3:44 ` Eli Zaretskii
2016-02-16 10:10 ` Dmitry Gutov
2016-02-16 16:01 ` Eli Zaretskii
2016-02-16 10:12 ` Dmitry Gutov
2016-02-17 1:55 ` Mike Kupfer [this message]
2016-02-19 13:43 ` Dmitry Gutov
2016-02-19 15:10 ` Mike Kupfer
2016-02-19 15:59 ` Eli Zaretskii
2016-02-19 18:08 ` Dmitry Gutov
2016-02-19 18:37 ` Eli Zaretskii
2016-02-19 18:52 ` Dmitry Gutov
2016-02-19 20:24 ` Eli Zaretskii
2016-02-20 1:28 ` Dmitry Gutov
2016-02-20 8:45 ` Eli Zaretskii
2016-02-21 3:36 ` Mike Kupfer
2016-02-21 22:56 ` Dmitry Gutov
2016-02-23 0:43 ` Dmitry Gutov
2016-02-23 2:19 ` Mike Kupfer
2016-02-18 3:45 ` bug#22692: docstring for xref-find-definitions Mike Kupfer
2016-02-18 16:50 ` Eli Zaretskii
2016-02-18 18:48 ` Mike Kupfer
2016-02-19 13:04 ` Dmitry Gutov
2016-02-19 13:01 ` Dmitry Gutov
2016-02-19 15:34 ` Eli Zaretskii
2016-02-20 1:24 ` Dmitry Gutov
2016-02-20 8:33 ` Eli Zaretskii
2016-02-23 0:04 ` Juri Linkov
2016-02-23 0:35 ` Dmitry Gutov
2016-02-27 10:32 ` Eli Zaretskii
2016-02-27 12:35 ` Dmitry Gutov
2016-02-27 12:43 ` Eli Zaretskii
2016-02-29 2:48 ` Dmitry Gutov
2016-02-23 0:41 ` Drew Adams
2016-02-21 3:42 ` Mike Kupfer
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=23698.1455674128@allegro.localdomain \
--to=m.kupfer@acm.org \
--cc=22692@debbugs.gnu.org \
--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).