From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
56197@debbugs.gnu.org, maxim.cournoyer@gmail.com
Subject: bug#56197: 28.1; lisp-fill-paragraph result regressed with Emacs 28
Date: Wed, 29 Jun 2022 11:03:11 -0700 [thread overview]
Message-ID: <CADwFkmmR8Edn7k33WUj6ytMx_VqqRce+UcVE6NVfXt9daNdauQ@mail.gmail.com> (raw)
In-Reply-To: <87tu88j3tf.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 25 Jun 2022 15:00:28 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I've now fixed that, but the question still remains -- should
>
> (foo-bar-zot-foo-bar-zot-foo-bar-zot-foo-bar-zot-foo-bar-zot "This is a very long line This is a very long line This is a very long line This")
>
> be filled as
>
> (foo-bar-zot-foo-bar-zot-foo-bar-zot-foo-bar-zot-foo-bar-zot "This is a very long line This is a very long line This is a very
> long line This")
>
> (i.e., fill the string using fill-column, or
>
> (foo-bar-zot-foo-bar-zot-foo-bar-zot-foo-bar-zot-foo-bar-zot "This is a
> very long line This is a very long line This is a very long line This")
>
> (i.e., fill the text as is in the buffer).
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.
next prev parent reply other threads:[~2022-06-29 18:03 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 [this message]
2022-06-30 9:32 ` Lars Ingebrigtsen
2022-06-30 9:33 ` Lars Ingebrigtsen
2022-06-30 11:31 ` Maxim Cournoyer
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=CADwFkmmR8Edn7k33WUj6ytMx_VqqRce+UcVE6NVfXt9daNdauQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=56197@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 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).