unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 14192@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully
Date: Tue, 16 Jan 2024 21:28:15 +0200	[thread overview]
Message-ID: <83sf2xaxio.fsf@gnu.org> (raw)
In-Reply-To: <87fryxkrqh.fsf@web.de> (message from Michael Heerdegen on Tue, 16 Jan 2024 20:23:02 +0100)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: stefankangas@gmail.com,  14192@debbugs.gnu.org
> Date: Tue, 16 Jan 2024 20:23:02 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I'm not opposed to patches to maybe make the C-r scenario less
> > surprising.  But in general, C-r is an obscure command in this case;
> > it isn't an accident that it was not even documented in the user
> > manual until recently.  The alternatives described above are IMO
> > better.
> 
> I've thought a while about it, also about improvements.  But I too came
> to the conclusion that the general approach of C-r is not optimal and we
> already have better alternatives, so I think telling the user to avoid
> the command and keep it for backward compatibility is the final solution
> for me.

Thanks.





  reply	other threads:[~2024-01-16 19:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 15:00 bug#14192: 24.3.50; recursive edit while running ispell not working usefully Michael Heerdegen
2013-04-12 16:51 ` Michael Heerdegen
2024-01-10 11:19   ` Stefan Kangas
2024-01-11  3:13     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11  6:49       ` Eli Zaretskii
2024-01-11 23:14         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13  7:57           ` Stefan Kangas
2024-01-14  1:13             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 20:35       ` Stefan Kangas
2024-01-11 23:30         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12  7:44         ` Eli Zaretskii
2024-01-14  1:25           ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  6:29             ` Eli Zaretskii
2024-01-16 19:23               ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 19:28                 ` Eli Zaretskii [this message]
2024-01-27  9:09               ` 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

  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=83sf2xaxio.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14192@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=stefankangas@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).