all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	maxim.cournoyer@gmail.com, 56197-done@debbugs.gnu.org
Subject: bug#56197: 28.1; lisp-fill-paragraph result regressed with Emacs 28
Date: Thu, 26 Dec 2024 15:16:34 +0000	[thread overview]
Message-ID: <CADwFkmm0zmNn2FjAbv4PscNDcuO0fHgn+AS01buKpAhdJ8QxXQ@mail.gmail.com> (raw)
In-Reply-To: <87mtducx7g.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> 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.
>
> Or -- perhaps it should be backported to Emacs 28 -- but not right now,
> since the release is impending.  So I'll keep this open until after
> Emacs 28.2, I think.

Emacs 28 was released on 2022-04-04, so I'm closing this bug now.





  reply	other threads:[~2024-12-26 15:16 UTC|newest]

Thread overview: 15+ 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
2024-12-26 15:16                 ` Stefan Kangas [this message]
2022-06-30 11:31               ` Maxim Cournoyer
2022-07-01  9:05                 ` Lars Ingebrigtsen
2024-12-25 20:15             ` Felix Lechner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-26  6:21               ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmm0zmNn2FjAbv4PscNDcuO0fHgn+AS01buKpAhdJ8QxXQ@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=56197-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=maxim.cournoyer@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.