unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43299@debbugs.gnu.org
Subject: bug#43299: 28.0.50; message-newline-and-reformat does not insert space after citation prefix
Date: Tue, 15 Sep 2020 10:31:43 -0400	[thread overview]
Message-ID: <87bli7kt68.fsf@gnu.org> (raw)
In-Reply-To: <87d02szf9i.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

Lars Ingebrigtsen writes:

> Amin Bandali <bandali@gnu.org> writes:
>
>> Thanks, it does seem to cover this case.  But now, there's a trailing
>> single space after the first '>' with no other characters after it.
>> Would it make sense to remove that once the filling/reformatting of the
>> paragraph is done?
>
> Hm...  I guess that's possibly (but sounds a bit finicky), but I'm not
> sure that's necessarily more correct than the old behaviour.

I think it would be more consistent, if not necessarily more correct, to
not insert that extraneous whitespace.

Also, I've noticed another side effect of this change: now even short
lines after point get filled, which is rather annoying.  For instance,
if you put the cursor after the first '>' and hit M-RET

--8<---------------cut here---------------start------------->8---
>
> Regards,
> X
> Y
--8<---------------cut here---------------end--------------->8---

you get:

--8<---------------cut here---------------start------------->8---
>



> 
> Regards, X Y
--8<---------------cut here---------------end--------------->8---

IMO filling should only be done when the line length exceeds the line
length limit, like it did before this change.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

  reply	other threads:[~2020-09-15 14:31 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
2020-09-10 21:45   ` Amin Bandali
2020-09-11 12:09     ` Lars Ingebrigtsen
2020-09-15 14:31       ` Amin Bandali [this message]
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=87bli7kt68.fsf@gnu.org \
    --to=bandali@gnu.org \
    --cc=43299@debbugs.gnu.org \
    --cc=larsi@gnus.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).