all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: maxim.cournoyer@gmail.com
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 16:19:27 +0200	[thread overview]
Message-ID: <867c7ad5lc.fsf@gnu.org> (raw)
In-Reply-To: <86ed1id6a3.fsf@gnu.org> (message from Eli Zaretskii on Sat, 04 Jan 2025 16:04:36 +0200)

> Cc: larsi@gnus.org, 56197@debbugs.gnu.org, felix.lechner@lease-up.com,
>  stefankangas@gmail.com
> Date: Sat, 04 Jan 2025 16:04:36 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
> > Cc: larsi@gnus.org,  56197@debbugs.gnu.org,  felix.lechner@lease-up.com,
> >   stefankangas@gmail.com
> > Date: Sat, 04 Jan 2025 19:09:42 +0900
> > 
> > >> 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.
> > >
> > > Having the behavior defined per-project or even globally (reverting to
> > > the the pre-Emacs 28 behavior) via a simple option seems like it'd
> > > simplify things, and make them discoverable.
> > 
> > I tried fixing this generally, as it seems to me that something in
> > lisp-mode should be meet the needs of all lisp-derived languages such as
> > Scheme and not just Elisp.  I first added two tests, one of which
> > ensures no regression to the original bug that lead to this current
> > behavioral change (bug#28937) and the other one that should pass once
> > the issue reported here (bug#56197) is resolved.
> > 
> > The last patch is a WIP that didn't work; I was hoping that inserting
> > spaces corresponding to the width of the indent in the narrowed string
> > would cause the indent to be preserved only for the first line.  I don't
> > have other ideas at the moment; I'd appreciate if someone could tip in.
> 
> Since you submitted a new bug report about this issue, does that mean
> these comments and the patches are no longer pertinent?

Sorry, I should have written "new patch", not "new bug report".





  reply	other threads:[~2025-01-04 14:19 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
2025-01-04 14:04                         ` Eli Zaretskii
2025-01-04 14:19                           ` Eli Zaretskii [this message]
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=867c7ad5lc.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.