From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 14192@debbugs.gnu.org
Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully
Date: Fri, 12 Jan 2024 00:30:10 +0100 [thread overview]
Message-ID: <87h6jjcut9.fsf@web.de> (raw)
In-Reply-To: <CADwFkmnBzKtqDaR8X9hVR4+jT+5g1aYz5a9L7i=Uv+O3BkWc3A@mail.gmail.com> (Stefan Kangas's message of "Thu, 11 Jan 2024 12:35:11 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> So do tell us if we make mistakes, but please be patient with us if we
> aren't always as polite or diligent as we are on our best days.
All good - see my reply to Eli. But please try to be as polite as
possible, given the mountain of bugs in front of you. I don't care
personally, but it's good to not leave a bad impression to others.
But maybe we can quickly handle this report? What's your opinion about
the behavior of Emacs?
AFAIR after I had made the report I had been told that for replacing
words I should use r or R instead of C-r aka recursive-edit (have a
better memory than I thought I would have...maybe it had been Eli). And
that the r-e is more for looking up words in a dictionary or such
things, not to make buffer changes. Nonetheless do I still dislike the
behavior of C-r. Does it make sense to you, does it have advantages I
don't see?
TIA,
Michael.
next prev parent reply other threads:[~2024-01-11 23:30 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 [this message]
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
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=87h6jjcut9.fsf@web.de \
--to=bug-gnu-emacs@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).