From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#57212: 29.0.50; [PATCH] Citizen's arrest of end-of-defun-moves-to-eol Date: Tue, 16 Aug 2022 08:14:46 +0000 Message-ID: <325f95fd2be1f7d43efb@heytings.org> References: <87k07au2i8.fsf@dick> <3a1232a17bcbf1cba5cc@heytings.org> <83czd0hqe0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3332"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57212@debbugs.gnu.org, dick.r.chiang@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 16 10:15:34 2022 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 1oNrja-0000ix-Dy for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Aug 2022 10:15:34 +0200 Original-Received: from localhost ([::1]:48360 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oNrjZ-0007bx-Gh for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Aug 2022 04:15:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48590) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNrj4-0007Zi-RR for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 04:15:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54954) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oNrj4-0001u1-IZ for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 04:15:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oNrj4-0007HM-Ea for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 04:15:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 16 Aug 2022 08:15:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57212 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch notabug Original-Received: via spool by 57212-submit@debbugs.gnu.org id=B57212.166063769027946 (code B ref 57212); Tue, 16 Aug 2022 08:15:02 +0000 Original-Received: (at 57212) by debbugs.gnu.org; 16 Aug 2022 08:14:50 +0000 Original-Received: from localhost ([127.0.0.1]:44703 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oNrir-0007Gg-KJ for submit@debbugs.gnu.org; Tue, 16 Aug 2022 04:14:49 -0400 Original-Received: from heytings.org ([95.142.160.155]:55370) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oNrip-0007GY-VT for 57212@debbugs.gnu.org; Tue, 16 Aug 2022 04:14:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1660637687; bh=3Xy0Sk5tP4GobE5yRGLlkosPVVX32Ne1PyiVZD7Og14=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=Mw6TuLWIhKdCKfz0zFzggho42NXn3xwRfZ4ZVvAOfBRTaTDnitrWlsM2wxSIdV5zC IOu7E9qX8VdMjMIszNv6ms2eIBmEJB5ppBKuCdemO4VDPpd28s06fz6dQlfjySqw/b QTmsFBioJYTPA/WKN7G7DdoCLz+KLGCyo0FLyVLS8sTHe7uIw9tR7TQcoZWA3qWGFX EaJWxhHOLQtUhl+6A7H0BNt9VZ7WfGjJ6DINQ0UOsLABsBcyYg9LWzqUvwqbM3adYG i5DC6Lb92jExQCUSyEPybEvys3Kp5OYZbJXGneJh+RT7cJrMpGaPteHUYjx+/yBg8v //yPYOUQs/wig== In-Reply-To: <83czd0hqe0.fsf@gnu.org> 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" Xref: news.gmane.io gmane.emacs.bugs:239878 Archived-At: >>> If you're convinced narrowing within a critical section of redisplay >>> is safe (and I suspect it is), do it all the time, not just when >>> "long_line_optimizations_p" is true. >> >> That might indeed be what Emacs could do in the long term, once we have >> enough experience with it. > > No, it shouldn't, because of the adverse effects of that on some aspects > of the Emacs behavior. > Indeed. I should have added something like "if we find a way to cope with these adverse effects".