From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: etags to xref changed navigation
Date: Tue, 23 Apr 2024 21:41:47 +0300 [thread overview]
Message-ID: <865xw753bo.fsf@gnu.org> (raw)
In-Reply-To: <jwvzftk2aw5.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 23 Apr 2024 14:29:31 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: help-gnu-emacs@gnu.org
> Date: Tue, 23 Apr 2024 14:29:31 -0400
>
> >> 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).
next prev parent reply other threads:[~2024-04-23 18:41 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 [this message]
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=865xw753bo.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).