From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>, William Xu <william.xwl@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Xref completion
Date: Thu, 3 Dec 2020 02:25:08 +0200 [thread overview]
Message-ID: <9bbe9827-8e96-e45c-2e0f-23a4fb5aea33@yandex.ru> (raw)
In-Reply-To: <87tut351ea.fsf@mail.linkov.net>
On 02.12.2020 23:44, Juri Linkov wrote:
>> One more point, I'm not sure if the order of the candidates are
>> important or not, but we can keep it the same order as in xref buffer.
>
> Yes, better to keep the same order.
>
> One additional question: is it possible to use only relative file names,
> relative to the project root dir? Absolute file names are too long.
Not always possible to do it against the project root
(xref-find-definitions does not depend on project.el), but you can still
find the longest parent directory and cut it off, similarly to how it's
done in project--read-file-cpd-relative.
> BTW, like you created xref--show-defs-minibuffer
> as a possible option for xref-show-definitions-function,
> wouldn't it be also nice to do the same and create
> xref--show-xref-minibuffer as a possible option for
> xref-show-xrefs-function?
Don't you usually want to iterate across multiple results, when the
command is project-find-regexp or xref-find-references? Then the same
logic will not work.
I mean, sometimes you probably want to find just one match, but changing
xref-show-xrefs-function will affect all invocations.
Or maybe I should ask: how will xref--show-xref-minibuffer be different
from xref--show-defs-minibuffer?
next prev parent reply other threads:[~2020-12-03 0:25 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 ` [SPAM UNSURE] " Stephen Leake
2020-11-17 18:32 ` 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 [this message]
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=9bbe9827-8e96-e45c-2e0f-23a4fb5aea33@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=william.xwl@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).