From: Eli Zaretskii <eliz@gnu.org>
To: michael_heerdegen@web.de
Cc: 14192-done@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully
Date: Sat, 27 Jan 2024 11:09:52 +0200 [thread overview]
Message-ID: <86zfwr87mn.fsf@gnu.org> (raw)
In-Reply-To: <83h6jgfmwi.fsf@gnu.org> (message from Eli Zaretskii on Sun, 14 Jan 2024 08:29:33 +0200)
> Cc: 14192@debbugs.gnu.org, stefankangas@gmail.com
> Date: Sun, 14 Jan 2024 08:29:33 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Cc: Stefan Kangas <stefankangas@gmail.com>, 14192@debbugs.gnu.org
> > Date: Sun, 14 Jan 2024 02:25:20 +0100
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > FTR: C-r indeed was not meant to be used to modify the misspelled
> > > word. ispell.el has 'r' and 'R' commands for that. C-r is for
> > > consulting the rest of the text, without modifying it and without
> > > disrupting the spelling session. An alternative is to type 'X', make
> > > any modifications you want, and then resume spelling with "C-u M-$".
> >
> > Thanks - especially for your concretizations of the spell checking
> > related parts in the user manual.
> >
> > I find it an a bit obscure design that there is C-r that reverses edits,
> > then X, which allows to resume the session, and C-g, which doesn't allow
> > resuming. Maybe less commands would suffice. But I don't use ispell
> > often, I can't really tell whether the interface is intuitive, and
> > nobody else seems to be interested in this topic.
>
> 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.
>
> > So, if we don't get any other replies until some more time has passed,
> > I'm ok with closing this one.
>
> Will do in a week or two.
Done.
prev parent reply other threads:[~2024-01-27 9:09 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
2024-01-27 9:09 ` Eli Zaretskii [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
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=86zfwr87mn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14192-done@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).