From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 56197@debbugs.gnu.org,
felix.lechner@lease-up.com, stefankangas@gmail.com
Subject: bug#56197: lisp-fill-paragraph behavior changed in Emacs 28
Date: Sat, 04 Jan 2025 19:14:20 +0900 [thread overview]
Message-ID: <87r05ievib.fsf@gmail.com> (raw)
In-Reply-To: <87v7uuevq1.fsf_-_@gmail.com> (Maxim Cournoyer's message of "Sat, 04 Jan 2025 19:09:42 +0900")
Hi again,
[...]
> If that's not easily fixable, perhaps I'll submit a patch to the paredit
> project so that they stop relying on lisp-paragraph-fill [0] and instead
> use the default (which is fill-paragraph). That's how I came to notice
> this behavior change in GNU Guix, which is written in Scheme; using
> scheme-mode doesn't exhibit the issue since it's just using
> fill-paragraph.
Actually, it seems scheme-mode at least in Emacs 29.4 does make use of
lisp-fill-paragraph, so should exhibit the same behavior/problem:
c.f. circa line 178 of scheme.el:
--8<---------------cut here---------------start------------->8---
(setq-local fill-paragraph-function 'lisp-fill-paragraph)
--8<---------------cut here---------------end--------------->8---
--
Thanks,
Maxim
next prev parent reply other threads:[~2025-01-04 10:14 UTC|newest]
Thread overview: 28+ 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
2024-12-28 5:52 ` Maxim Cournoyer
2024-12-28 8:47 ` Eli Zaretskii
2024-12-28 14:51 ` Maxim Cournoyer
2024-12-28 8:52 ` Stefan Kangas
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
2024-12-28 5:26 ` Maxim Cournoyer
2024-12-28 8:45 ` Eli Zaretskii
2024-12-28 15:14 ` Maxim Cournoyer
2025-01-04 10:09 ` bug#56197: lisp-fill-paragraph behavior changed in " Maxim Cournoyer
2025-01-04 10:14 ` Maxim Cournoyer [this message]
2025-01-04 14:04 ` Eli Zaretskii
2025-01-04 14:19 ` Eli Zaretskii
2022-06-27 1:53 ` bug#56197: 28.1; lisp-fill-paragraph result regressed with " Maxim Cournoyer
2025-01-04 13:03 ` bug#56197: [PATCH] lisp: Introduce lisp-fill-paragraph-as-displayed option Maxim Cournoyer
2025-01-04 14:02 ` Eli Zaretskii
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=87r05ievib.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=56197@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=larsi@gnus.org \
--cc=stefankangas@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.