From: Philip Kaludercic <philipk@posteo.net>
To: Phillip Susi <phill@thesusis.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: etags to xref changed navigation
Date: Tue, 23 Apr 2024 19:33:53 +0000 [thread overview]
Message-ID: <87ttjrlvq6.fsf@posteo.net> (raw)
In-Reply-To: <87a5lk6lrw.fsf@vps.thesusis.net> (Phillip Susi's message of "Tue, 23 Apr 2024 13:17:55 -0400")
Phillip Susi <phill@thesusis.net> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Not necessarily, you can use M-g M-n and M-g M-p from the buffer you
>> invoked xref in to navigate definitions as well.
>
> Ahh, that does the trick, just with two chords instead of one.
Note that these are just the next-error and previous-error functions.
You could just as well (re)bind them to whatever other key you prefer,
if you feel that this is something you use frequently enough. I
personally find the M- prefix simple and convenient enough to not need a
shorter chord.
> And a
> C-x 0 to dismiss the xref buffer first.
You could change this by setting xref-show-definitions-function to the
right function.
--
Philip Kaludercic on peregrine
prev parent reply other threads:[~2024-04-23 19:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 15:11 etags to xref changed navigation Phillip Susi
2024-04-22 15:30 ` Eli Zaretskii
2024-04-22 16:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-22 19:19 ` Eli Zaretskii
2024-04-23 1:39 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-23 17:06 ` Phillip Susi
2024-04-23 18:29 ` Stefan Monnier
2024-04-23 18:41 ` Eli Zaretskii
2024-04-24 2:07 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-04-24 6:31 ` Eli Zaretskii
2024-04-25 0:05 ` Dmitry Gutov
2024-04-25 3:34 ` Stefan Monnier
2024-04-25 21:30 ` Dmitry Gutov
2024-04-23 17:02 ` Phillip Susi
2024-04-23 17:15 ` Eli Zaretskii
2024-04-22 17:48 ` Philip Kaludercic
2024-04-23 17:17 ` Phillip Susi
2024-04-23 19:33 ` Philip Kaludercic [this message]
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=87ttjrlvq6.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=phill@thesusis.net \
/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.