From: Ludovic Brenta <ludovic@ludovic-brenta.org>
To: 32510@debbugs.gnu.org
Subject: bug#32510: xref-find-definitions should return file names, too
Date: Thu, 18 Jul 2019 16:53:42 +0200 [thread overview]
Message-ID: <b8f087f2fa5c8680fa90a77a147286c5@ludovic-brenta.org> (raw)
In-Reply-To: <a3594dbf23c19addc79652c8729a06bc@ludovic-brenta.org>
tags 32510 - wontfix
thanks
I can confirm that the patch by Eli Zaretskii works, with a
difference compared to find-tag: find-tag opens the first
file whose name matches the searched string whereas
xref-find-definitions opens a new buffer with all matches,
forcing the user to use many keystrokes (or worse: reach
for the mouse :)) to choose a match.
I suppose this change of behavior is intentional, consistent
with all other cross-references, and only affects ergonomy;
the patch more importantly restores the functionality that
was previously lost.
--
Ludovic Brenta.
next prev parent reply other threads:[~2019-07-18 14:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ftnazlz3.fsf@mouse.gnus.org>
2018-08-23 15:32 ` bug#32510: xref-find-definitions should return file names, too Ludovic Brenta
2019-07-13 2:50 ` Lars Ingebrigtsen
[not found] ` <handler.32510.C.15629862456126.notifdonectrl.0@debbugs.gnu.org>
2019-07-13 19:34 ` bug#32510: acknowledged by developer (control message for bug #32510) Ludovic Brenta
2019-07-13 23:25 ` Drew Adams
2019-07-14 5:21 ` Eli Zaretskii
2019-07-30 0:06 ` Dmitry Gutov
2019-07-30 14:00 ` Dmitry Gutov
2019-08-03 10:00 ` Eli Zaretskii
2019-07-15 13:54 ` bug#32510: Tags: wontfix -> patch Ludovic Brenta
2019-07-18 14:53 ` Ludovic Brenta [this message]
2019-07-18 15:16 ` bug#32510: xref-find-definitions should return file names, too Eli Zaretskii
2019-07-18 15:54 ` Ludovic Brenta
2019-07-18 16:07 ` Eli Zaretskii
2019-07-19 22:23 ` Dmitry Gutov
2019-07-20 7:17 ` 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=b8f087f2fa5c8680fa90a77a147286c5@ludovic-brenta.org \
--to=ludovic@ludovic-brenta.org \
--cc=32510@debbugs.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.