all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: etags to xref changed navigation
Date: Wed, 24 Apr 2024 09:31:02 +0300	[thread overview]
Message-ID: <86y1932rx5.fsf@gnu.org> (raw)
In-Reply-To: <jwvh6frikjl.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier via Users list for the GNU Emacs text editor on Tue, 23 Apr 2024 22:07:08 -0400)

> Date: Tue, 23 Apr 2024 22:07:08 -0400
> From:  Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> >> >> I'm not sure what the problems would be, concretely, but we can always
> >> >> solve the problem by making the behavior optional.
> >> > I think the reason why it was on M-, before was because repeated
> >> > M-. couldn't tell whether you wanted the next, or to start a new search
> >> > for whatever point is on now.
> >> 
> >> That's also my understanding, and I'm suggesting that it distinguishes
> >> the two by checking if `M-.` is used consecutively or not
> >
> > The problem with this proposal is that any command in-between will
> > break the chain.  One must remember not event to move point.  That
> > could well be problematic: for example, imagine that I'm not sure
> > whether I want the current candidate, and to be sure I need to scroll
> > the window a bit, because what M-. displayed doesn't show enough
> > (e.g., because the window is too small).
> 
> IIUC if you break the chain, indeed you wouldn't be able to use `M-.` to
> keep going to the next def, but you could still use `M-g M-n` for that.
> The extra keyboard movement from `M-.` to `M-g M-n` is expected to be
> much less of a burden since you presumably already moved your fingers
> away from `M-.` to break the chain.

That's correct, but I think remembering to use only "M-g M-n" is
easier, and together with xref-auto-jump-to-first-definition set to t
it should provide a UX almost identical to the old UX.



  reply	other threads:[~2024-04-24  6:31 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y1932rx5.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.
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.