From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: emacs-devel@gnu.org
Subject: Re: [SPAM UNSURE] Xref completion
Date: Tue, 17 Nov 2020 10:22:42 -0800 [thread overview]
Message-ID: <86ima3onbh.fsf@stephe-leake.org> (raw)
In-Reply-To: <873617ets1.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Tue, 17 Nov 2020 19:13:18 +0100")
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Hello!
>
> Currently, when a xref query hits multiple candidates Emacs shows a Xref
> buffer with the various candidates and their location.
>
> While informative, it's a bit slow in terms of UX because the user has
> to navigate an extra buffer just to confirm the candidate.
>
> I've addressed this issue as part of my work on Helm-SLY, a Helm for the
> fork of SLIME.
>
> https://github.com/emacs-helm/helm-sly
>
> In particular, I've overridden the behaviour with regards to Xrefs and
> instead of showing the Xref buffer, I'm now offering completion: the
> user can match against the symbol but also against the file and line
> position.
>
> See screenshot attached.
>
> What do you think of adding this behaviour to upstream Emacs' xref?
Sometimes choosing a single definition is what you want, other times you
want to see the list. So this would have to use a different keybinding
or prefix.
--
-- Stephe
Written from unceded ancestral homelands of the Huichiun, an Ohlone
people,for which I pay Shuumi Land Tax
(https://sogoreate-landtrust.com/shuumi-land-tax) as an inadequate token
of reparation.
next prev parent reply other threads:[~2020-11-17 18:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 18:13 Xref completion Pierre Neidhardt
2020-11-17 18:22 ` Stephen Leake [this message]
2020-11-17 18:32 ` [SPAM UNSURE] " Pierre Neidhardt
2020-11-17 18:46 ` Basil L. Contovounesios
2020-11-17 18:38 ` Eli Zaretskii
2020-11-17 19:11 ` Pierre Neidhardt
2020-11-17 19:27 ` Juri Linkov
2020-11-17 20:00 ` Dmitry Gutov
2020-11-17 21:16 ` William Xu
2020-11-17 21:38 ` Dmitry Gutov
2020-11-18 7:35 ` William Xu
2020-11-18 13:46 ` Dmitry Gutov
2020-11-18 18:53 ` William Xu
2020-11-18 19:22 ` Dmitry Gutov
2020-11-18 20:39 ` Juri Linkov
2020-11-19 1:34 ` Dmitry Gutov
2020-11-18 18:47 ` João Távora
2020-11-19 1:43 ` Dmitry Gutov
2020-11-19 8:19 ` William Xu
2020-11-19 13:30 ` Dmitry Gutov
2020-12-02 21:44 ` Juri Linkov
2020-12-03 0:25 ` Dmitry Gutov
2020-12-03 21:09 ` Juri Linkov
2020-12-05 1:12 ` Dmitry Gutov
2020-12-05 12:21 ` William Xu
2020-12-05 21:02 ` Dmitry Gutov
2020-12-06 8:30 ` William Xu
2020-12-06 11:00 ` Dmitry Gutov
2020-12-06 14:00 ` William Xu
2020-12-06 21:01 ` Dmitry Gutov
2020-12-05 19:52 ` Juri Linkov
2020-12-05 21:44 ` Dmitry Gutov
2020-12-06 20:46 ` Juri Linkov
2020-12-06 21:20 ` Dmitry Gutov
2020-12-06 21:34 ` Juri Linkov
2020-12-06 21:40 ` Dmitry Gutov
2020-12-07 9:27 ` Daniel Martín
2020-12-07 15:12 ` jixiuf
2020-12-07 21:57 ` Dmitry Gutov
2020-12-07 21:53 ` 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=86ima3onbh.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).