From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22692@debbugs.gnu.org, juri@linkov.net, m.kupfer@acm.org
Subject: bug#22692: docstring for xref-find-definitions
Date: Sat, 27 Feb 2016 14:43:04 +0200 [thread overview]
Message-ID: <83twkub9yf.fsf@gnu.org> (raw)
In-Reply-To: <e40e3de7-40f9-909c-5b03-6fe1add9858c@yandex.ru> (message from Dmitry Gutov on Sat, 27 Feb 2016 14:35:20 +0200)
> Cc: 22692@debbugs.gnu.org, juri@linkov.net, m.kupfer@acm.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 27 Feb 2016 14:35:20 +0200
>
> On 02/27/2016 12:32 PM, Eli Zaretskii wrote:
>
> > The current doc string looks OK to me: it describes the behavior very
> > well.
>
> Great. I believe the only thing holding this bug is making the choice
> about the "valid" in the manual.
You mean, whether to remove the "valid" part from the 2nd sentence
reproduced below?
‘M-.’ (‘xref-find-definitions’) shows the definitions of the
identifier at point. With a prefix argument, or if there’s no valid
identifier at point, it prompts for the identifier. ^^^^^
I'd say let's remove it.
next prev parent reply other threads:[~2016-02-27 12:43 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
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 [this message]
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=83twkub9yf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22692@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
--cc=m.kupfer@acm.org \
/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).