From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#56197: lisp-fill-paragraph behavior changed in Emacs 28 Date: Sat, 04 Jan 2025 16:04:36 +0200 Message-ID: <86ed1id6a3.fsf@gnu.org> References: <87zgi2xcgm.fsf@gmail.com> <87y1xlj6wn.fsf@gnus.org> <834k08c3se.fsf@gnu.org> <874k08kj31.fsf@gnus.org> <87y1xkj4co.fsf@gnus.org> <87tu88j3tf.fsf@gnus.org> <87bjwzr027.fsf@lease-up.com> <86v7v7ynf0.fsf@gnu.org> <87seq8tm2f.fsf@gmail.com> <86o70wurf9.fsf@gnu.org> <87ttanrg9h.fsf@gmail.com> <87v7uuevq1.fsf_-_@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19921"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, 56197@debbugs.gnu.org, felix.lechner@lease-up.com, stefankangas@gmail.com To: Maxim Cournoyer Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jan 04 15:05:20 2025 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tU4mG-00053S-Co for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 04 Jan 2025 15:05:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tU4m1-0001M6-Or; Sat, 04 Jan 2025 09:05:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tU4lz-0001L9-2Q for bug-gnu-emacs@gnu.org; Sat, 04 Jan 2025 09:05:04 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tU4ly-0007sm-Mm for bug-gnu-emacs@gnu.org; Sat, 04 Jan 2025 09:05:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=fYorwKKVV0PtYXfEDLZhYH8Ydaxfvhv8w9xClwaDCIA=; b=vek8rn799+AeUXl6M8AKfDh88vCCsnSCoeOqnMUPi3Ag1TZCdA1NpaqF1pGaQSqySuYo5BpjilQTB6622m0sWzIsw0ru3xp1n9LAvpCRTOTzA/89R4CEkiwodT9icojKqaVCGP2+ChdCQPfhNccV2vwBLY5k7E+bTLfBWcx4wDZ8pBmAD+ELXo/R7AVJUu3pR8h18AZiX61uyWWIRws4tBA01VEomtVKdc59MSVldeSBTvyS60h4gozgvEXQLLxp+lps0/iszKZb0DKZo1WBdbEQQ+mIUjnv452v30a6cLrTVKtANcRfi3tZesHQ0Gx4TImVHJG5VQfoMfnjkQn/bA==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tU4ly-0001HQ-Fa for bug-gnu-emacs@gnu.org; Sat, 04 Jan 2025 09:05:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 04 Jan 2025 14:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56197 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 56197-submit@debbugs.gnu.org id=B56197.17359994874892 (code B ref 56197); Sat, 04 Jan 2025 14:05:02 +0000 Original-Received: (at 56197) by debbugs.gnu.org; 4 Jan 2025 14:04:47 +0000 Original-Received: from localhost ([127.0.0.1]:53982 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tU4lj-0001Go-6m for submit@debbugs.gnu.org; Sat, 04 Jan 2025 09:04:47 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51096) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1tU4lg-0001GY-Nv for 56197@debbugs.gnu.org; Sat, 04 Jan 2025 09:04:45 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tU4lb-0007jR-DS; Sat, 04 Jan 2025 09:04:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=fYorwKKVV0PtYXfEDLZhYH8Ydaxfvhv8w9xClwaDCIA=; b=mTXYPLyWAMwI rtGSHnrCPSNcJkhBP6bkrZzULmt9C6dTXmddAJ9C/lFPc5fNfgClshqUeyHcPUvkUurpCrddzBmj6 R9Xvk2VB7EC8RUv00MKo8PasL74m4s2ypDV/r9Mw/3+XU/+KwlJiGnTKRDzgV5QaMzSHrH3+gLzuJ fzX5nSUO/OjYs8rwzVoxrmQopiwK+pnWG/oz9pJ/mV0L+vARTIzlYZ8hEHys0qeIEcc6QLg9MIz8S 6Od2U2kXXZKT9FupwGRhRiyOocCisSO9WcT+/IIMszEh/yUBmtaw8YRW/dUzo30BKxVtrdkJ9dr2J fbD6BXHPo2KZFz0Lbbnt1A==; In-Reply-To: <87v7uuevq1.fsf_-_@gmail.com> (message from Maxim Cournoyer on Sat, 04 Jan 2025 19:09:42 +0900) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298406 Archived-At: > From: Maxim Cournoyer > 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?