all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [xref.el] Add `xref-find-references` to `xref-prompt-for-identifier`
Date: Sat, 09 Dec 2017 10:29:48 +0200	[thread overview]
Message-ID: <83lgicuww3.fsf@gnu.org> (raw)
In-Reply-To: <CAN30aBF0FcQpH+DDxR5ggWgwYHPn41nzdgNdUXSt2j0mXY39-A@mail.gmail.com> (message from Ray on Fri, 8 Dec 2017 13:13:49 -0800)

> From: Ray <emacsray@gmail.com>
> Date: Fri, 8 Dec 2017 13:13:49 -0800
> 
> 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.
> 
> Many language servers now support finding references. The typical
> usage of lsp-mode is to put point at some identifier and hit a
> shortcut (by default M-?) to trigger xref-find-references. The prompt
> is in many cases undesired.

Please either post this to emacs-devel@gnu.org, or (better) use
report-emacs-bug to request this addition.  The latter causes your
request to be recorded by the Emacs issue tracker; both methods will
have the request sent to people who are actually developing xref.el.

Thanks.



  parent reply	other threads:[~2017-12-09  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 21:13 [xref.el] Add `xref-find-references` to `xref-prompt-for-identifier` Ray
2017-12-08 21:27 ` bug#29619: Fwd: " 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
2017-12-09  8:29 ` Eli Zaretskii [this message]
2017-12-09  8:59   ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lgicuww3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.