unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Stefan Kangas <stefan@marxist.se>
Cc: Eli Zaretskii <eliz@gnu.org>, 56197@debbugs.gnu.org
Subject: bug#56197: 28.1; lisp-fill-paragraph result regressed with Emacs 28
Date: Thu, 30 Jun 2022 07:31:55 -0400	[thread overview]
Message-ID: <5742C214-5A0B-45B7-B9BA-D1E907C79A2B@gmail.com> (raw)
In-Reply-To: <87r136cx9j.fsf@gnus.org>

On June 30, 2022 5:32:08 AM EDT, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>Stefan Kangas <stefan@marxist.se> writes:
>
>> The former sounds more useful, IMO.  I don't want to mess up my strings
>> just to have pretty source code; I can make such adjustments manually
>> when I need to.
>
>So the votes are in, and I guess we'll keep the current behaviour in
>Emacs 29, and I'm therefore closing this bug report.
>

Just to make sure, this means the paragraph filling behavior seen in the examples I shared would be unchanged, and different from that in Emacs 27 and earlier, correct?

To me, the previous behavior was useful; is there a way to configure Emacs to behave that way with Emacs 28?

Thank you!

Maxim
Hi,





  parent reply	other threads:[~2022-06-30 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 16:17 bug#56197: 28.1; lisp-fill-paragraph result regressed with Emacs 28 Maxim Cournoyer
2022-06-25 11:53 ` Lars Ingebrigtsen
2022-06-25 12:42   ` Eli Zaretskii
2022-06-25 12:45     ` Lars Ingebrigtsen
2022-06-25 12:48       ` Lars Ingebrigtsen
2022-06-25 13:00         ` Lars Ingebrigtsen
2022-06-29 18:03           ` Stefan Kangas
2022-06-30  9:32             ` Lars Ingebrigtsen
2022-06-30  9:33               ` Lars Ingebrigtsen
2022-06-30 11:31               ` Maxim Cournoyer [this message]
2022-07-01  9:05                 ` Lars Ingebrigtsen
2022-06-27  1:53   ` Maxim Cournoyer

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=5742C214-5A0B-45B7-B9BA-D1E907C79A2B@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=56197@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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).