unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gabriel do Nascimento Ribeiro <gabriel376@hotmail.com>
To: emacs-devel@gnu.org
Subject: Re: Consistency for xref-show-{xrefs,definitions}-function
Date: Sat, 16 Jan 2021 15:35:51 -0300	[thread overview]
Message-ID: <CH2PR01MB5879E61CE4C5C306FB474BAC8BA60@CH2PR01MB5879.prod.exchangelabs.com> (raw)
In-Reply-To: <a5ff2cd3-f08d-a0ef-c6cc-bd0082536dff@yandex.ru> (Dmitry Gutov's message of "Fri, 15 Jan 2021 19:20:34 +0200")

>
> Why do you want this?
>
> xref-find-definitions differs from the rest of Xref-using commands in
> that it usually only find one location, and when there are several,
> the user wants to quickly choose one of the alternatives, the faster
> the better. The different options for xref-show-definitions-function
> provide different solutions for that problem.
>
> In all other cases returning multiple results is the common case, and
> you usually want to see all of them, not just one. For that, the
> completing-read UI, for example, is not very suitable.

Thanks for the inputs.

My use case is: when inside a project, the only option to jump to a
certain location is by using 'C-x p g' (which runs 'xref--show-xrefs')
and selecting the desired location from the list of matches in a
separated buffer. I would like to be able to select a single element
from this list of matches, preferably with 'completing-read'.

I took another look in the code, so I guess we can keep the xrefs
functions as it is and tweak 'project-find-regexp' to be more flexible
on this.





  reply	other threads:[~2021-01-16 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 20:27 Consistency for xref-show-{xrefs,definitions}-function Gabriel do Nascimento Ribeiro
2021-01-14 21:04 ` Daniel Martín
2021-01-15 17:20 ` Dmitry Gutov
2021-01-16 18:35   ` Gabriel do Nascimento Ribeiro [this message]
2021-01-16 19:24     ` Dmitry Gutov
2021-01-16 20:31       ` Gabriel do Nascimento Ribeiro
2021-01-18  1:28         ` 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=CH2PR01MB5879E61CE4C5C306FB474BAC8BA60@CH2PR01MB5879.prod.exchangelabs.com \
    --to=gabriel376@hotmail.com \
    --cc=emacs-devel@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 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).