From: Lars Ingebrigtsen <larsi@gnus.org>
To: <spwhitton@spwhitton.name>
Cc: Andreas Schwab <schwab@suse.de>, 56384@debbugs.gnu.org
Subject: bug#56384: 29.0.50; backward-word doesn't move far enough in message-mode
Date: Tue, 05 Jul 2022 18:44:40 +0200 [thread overview]
Message-ID: <87k08r1pc7.fsf@gnus.org> (raw)
In-Reply-To: <87tu7vljau.fsf@athena.silentflame.com> (spwhitton@spwhitton.name's message of "Tue, 05 Jul 2022 07:34:49 -0700")
<spwhitton@spwhitton.name> writes:
> I noticed this bug because it breaks expanding abbrevs at the beginning
> of the line. E.g. you've just pressed 'R' to reply with quoting the
> original message in Gnus, and point is at the beginning of the first
> quoted line. Then if you type a word that is the key for an abbrev, and
> then whitespace, it won't expand. I wonder if that can be fixed without
> losing the benefits of João's change.
I'm not quite sure the change makes all that much sense. If you have
this:
---
foo
> bar
zot
---
with point after foo, `M-C-f' takes you to the end of zot, which is
surprising.
I guess the idea is that you'd never want to edit quoted text?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-05 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 16:04 bug#56384: 29.0.50; backward-word doesn't move far enough in message-mode Sean Whitton
2022-07-05 11:29 ` Lars Ingebrigtsen
2022-07-05 11:43 ` Andreas Schwab
2022-07-05 11:52 ` Lars Ingebrigtsen
2022-07-05 14:34 ` spwhitton
2022-07-05 16:44 ` Lars Ingebrigtsen [this message]
2022-07-05 17:04 ` Eli Zaretskii
2022-07-05 17:09 ` Lars Ingebrigtsen
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=87k08r1pc7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=56384@debbugs.gnu.org \
--cc=schwab@suse.de \
--cc=spwhitton@spwhitton.name \
/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).