unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: etags to xref changed navigation
Date: Mon, 22 Apr 2024 22:19:34 +0300	[thread overview]
Message-ID: <86bk615ho9.fsf@gnu.org> (raw)
In-Reply-To: <jwvh6ftl77z.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier via Users list for the GNU Emacs text editor on Mon, 22 Apr 2024 12:00:39 -0400)

> Date: Mon, 22 Apr 2024 12:00:39 -0400
> From:  Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> > If you still want to have the old behavior back, you can rebind M-. to
> > find-tag and M-, to tags-loop-continue, which still exist, just
> > without the default key binding.
> 
> But these use only the TAGS info, not the Xref info.

That's what the pre-Emacs 25 M-. and M-, did.  So if that was good
enough then, find-tag should be good enough now.

> Maybe we could make consecutive uses of `M-.` jump to the "next def"
> (when there are more than one)?

That'd get in the way of some workflows, I think, and is also very
problematic from the UI POV.



  reply	other threads:[~2024-04-22 19:19 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 [this message]
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

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=86bk615ho9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).