From: Eli Zaretskii <eliz@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: larsi@gnus.org, 56197@debbugs.gnu.org,
felix.lechner@lease-up.com, stefankangas@gmail.com
Subject: bug#56197: 28.1; lisp-fill-paragraph result regressed with Emacs 28
Date: Sat, 28 Dec 2024 10:45:30 +0200 [thread overview]
Message-ID: <86o70wurf9.fsf@gnu.org> (raw)
In-Reply-To: <87seq8tm2f.fsf@gmail.com> (message from Maxim Cournoyer on Sat, 28 Dec 2024 14:26:32 +0900)
> From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Cc: Felix Lechner <felix.lechner@lease-up.com>, 56197@debbugs.gnu.org,
> stefankangas@gmail.com, larsi@gnus.org
> Date: Sat, 28 Dec 2024 14:26:32 +0900
>
> I can't say it feels very satisfactory; a switch like one imagined by
> Felix could be a step in the right direction; it'd be at least more
> concise in the project .dir-locals. Would a patch implementing that be
> welcome?
I don't see how a user option to control this could be useful, since
the preferred behavior is not only buffer-local, but also specific to
certain syntactic constructs. But I won't object to having such an
option.
I also don't see what's wrong with the solution of having a special
function in .dir-locals.el. We don't pretend that the default Emacs
behavior should necessarily fit all the use cases, and provide ample
opportunities for customizing Emacs behavior for that reason.
Defining a custom fill-paragraph function is a perfectly valid
solution, not very different from having a user option for the same
purpose. So I'm not sure I understand why you prefer adding an
option, when the Guix project has already solved the problem in a
perfectly legitimate and clean way.
next prev parent reply other threads:[~2024-12-28 8:45 UTC|newest]
Thread overview: 22+ 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 [this message]
2024-12-28 15:14 ` Maxim Cournoyer
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=86o70wurf9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56197@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=larsi@gnus.org \
--cc=maxim.cournoyer@gmail.com \
--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.