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#56393: Resetting long_line_optimization_p to 0 Date: Tue, 19 Jul 2022 09:51:02 +0000 Message-ID: References: <38c1a31040d2d2bc47ae@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20369"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56393@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jul 19 11:53:25 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 1oDjuv-00057A-FI for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 19 Jul 2022 11:53:25 +0200 Original-Received: from localhost ([::1]:33122 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oDjuu-00080b-CF for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 19 Jul 2022 05:53:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48048) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oDjta-0005w0-DF for bug-gnu-emacs@gnu.org; Tue, 19 Jul 2022 05:52:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55140) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oDjta-0003sp-25 for bug-gnu-emacs@gnu.org; Tue, 19 Jul 2022 05:52:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oDjtZ-0004qu-Ue for bug-gnu-emacs@gnu.org; Tue, 19 Jul 2022 05:52:01 -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, 19 Jul 2022 09:52:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56393 X-GNU-PR-Package: emacs Original-Received: via spool by 56393-submit@debbugs.gnu.org id=B56393.165822426918556 (code B ref 56393); Tue, 19 Jul 2022 09:52:01 +0000 Original-Received: (at 56393) by debbugs.gnu.org; 19 Jul 2022 09:51:09 +0000 Original-Received: from localhost ([127.0.0.1]:52888 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oDjsi-0004pD-VH for submit@debbugs.gnu.org; Tue, 19 Jul 2022 05:51:09 -0400 Original-Received: from heytings.org ([95.142.160.155]:43732) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oDjsd-0004oy-Ef for 56393@debbugs.gnu.org; Tue, 19 Jul 2022 05:51:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1658224262; bh=9md7oU/3/1JoxoCdBxfYlkG4+zQ//TlTQFp/vykB4+Q=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=VO+ojGoZsFRg0cs/nhkN9dkVuNT1VY47+i0TLBLnuSwgHQglD3yFkc9bryzC3NIbe YJVP+hhpSrdAob5ArdCxKYYI2peCYxsQlb47faR6uIEgpGiXR7lDTEyN/R/oy8Fu5k RGMiXdUaeCE/Uay4u/hCE/Z8mxKIdNE+QWkxugJOVe2c/9ejLCJre6K4i/vScEfaKm HEbZs78F8bN/l8C4HXbGhxM2RneyGTk33sMbXR1Zmc3z9GQVkcmX/Ek2TBoyaTci9J f/cT9z0uzTFVm5/EA/tO2i2DMQMsjFYt3mpiMi+AxqUZ/uj7MnW+ymHOqu7IIjaFMG 3H4NCow3siwKQ== In-Reply-To: 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:237418 Archived-At: > > What I meant was resetting the flag without resetting the buffer. For > example in redisplay_window when it finds that the condition for setting > it true is no longer met. > It is indeed never reset. It goes only in one direction: as soon as a buffer contains one "long enough" line, the specific optimizations are used, and the buffer continues to use them. Such buffers are not common, I don't think it is necessary/useful to check after each iteration whether the buffer still contains long lines, especially given that these optimizations have a near-nil effect in buffers without long lines.