From: guillaume papin <guillaume.papin@epitech.eu>
To: "29619@debbugs.gnu.org" <29619@debbugs.gnu.org>,
"dgutov@yandex.ru" <dgutov@yandex.ru>
Cc: "emacsray@gmail.com" <emacsray@gmail.com>
Subject: bug#29619: Fwd: [xref.el] Add `xref-find-references` to `xref-prompt-for-identifier`
Date: Sun, 21 Jan 2018 22:20:24 +0000 [thread overview]
Message-ID: <HE1PR02MB1195E8B29D95AD9CBF46D9DC8DED0@HE1PR02MB1195.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <CAN30aBHXrGGGGFsV5cUPQR6+mBCG950NJ_r=L7ijn3DO7cta3A@mail.gmail.com>
On 2017/12/09 5:25 PM, Dmitry Gutov wrote:
> On 12/8/17 11:27 PM, Ray wrote:
> > Currently, xref-find-references prompts for the identifier to look up,
> > because it is not listed in xref-prompt-for-identifier:
> >
> > (defcustom xref-prompt-for-identifier '(not xref-find-definitions
> > xref-find-definitions-other-window
> > xref-find-definitions-other-frame)
> >
> > It will be much core convenient to add xref-find-references in the list.
>
> We've discussed it before, and for now have settled on this list of
> non-prompting functions.
>
> But thank you for your report. We may change the default if more people
> feel the same.
Just wanted to chime in to say that I feel the same as Ray.
The commands already have related keybindings, M-. and M-?.
I would find it more intuitive, if they also had similar behaviors.
prev parent reply other threads:[~2018-01-21 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN30aBF0FcQpH+DDxR5ggWgwYHPn41nzdgNdUXSt2j0mXY39-A@mail.gmail.com>
2017-12-08 21:27 ` bug#29619: Fwd: [xref.el] Add `xref-find-references` to `xref-prompt-for-identifier` Ray
2017-12-09 15:25 ` Dmitry Gutov
2017-12-09 17:52 ` Ray
2017-12-10 16:57 ` Dmitry Gutov
2017-12-11 7:18 ` Fangrui Song
2017-12-11 10:38 ` Dmitry Gutov
2018-01-21 22:20 ` guillaume papin [this message]
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=HE1PR02MB1195E8B29D95AD9CBF46D9DC8DED0@HE1PR02MB1195.eurprd02.prod.outlook.com \
--to=guillaume.papin@epitech.eu \
--cc=29619@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacsray@gmail.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).