From: Lars Ingebrigtsen <larsi@gnus.org>
To: Amin Bandali <bandali@gnu.org>
Cc: 43299@debbugs.gnu.org
Subject: bug#43299: 28.0.50; message-newline-and-reformat does not insert space after citation prefix
Date: Thu, 10 Sep 2020 23:28:27 +0200 [thread overview]
Message-ID: <877dt148zo.fsf@gnus.org> (raw)
In-Reply-To: <877dt24orw.fsf@gnu.org> (Amin Bandali's message of "Wed, 09 Sep 2020 17:35:15 -0400")
Amin Bandali <bandali@gnu.org> writes:
> Currently, the `message-newline-and-reformat' function (bound to M-RET
> in `message-mode') does not insert an empty space after the citation
> prefix (e.g. '>') when reformatting the lines following the point in a
> common use scenario. I would like the behaviour to change, or at least
> an option be added to have `message-newline-and-reformat' insert a space
> after each '>'.
>
> Example:
>
>> test0
>>
>> test1 test2 test3 test4 test5 test6 test7 test8 test9 test10 test11 test12
The problem here is that there's no space after that > character. If it
had been
> test0
>
> test1 test2 test3 test4 test5 test6 test7 test8 test9 test10 test11 test12
instead (if that trailing space survives the mailing process) then you get
> test0
>
>
> test1 test2 test3 test4 test5 test6 test7 test8 test9 test10 test11
> test12
Hm... OK, I think I found it -- I think there was a reversed check for
the length of the spaces in the following paragraph? I pushed a fix to
Emacs 28 that seems to fix this use case, but I'm not exactly confident
that this doesn't introduce other oddities.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-10 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 21:35 bug#43299: 28.0.50; message-newline-and-reformat does not insert space after citation prefix Amin Bandali
2020-09-10 21:28 ` Lars Ingebrigtsen [this message]
2020-09-10 21:45 ` Amin Bandali
2020-09-11 12:09 ` Lars Ingebrigtsen
2020-09-15 14:31 ` Amin Bandali
2020-09-17 14:35 ` 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=877dt148zo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43299@debbugs.gnu.org \
--cc=bandali@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.
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).