From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#56682: feature/improved-locked-narrowing 9dee6df39c: Reworked locked narrowing. Date: Mon, 30 Jan 2023 19:24:56 +0200 Organization: LINKOV.NET Message-ID: <864js8gck7.fsf@mail.linkov.net> References: <166939872890.18950.12581667269687468681@vcs2.savannah.gnu.org> <20221125175209.51166C004B6@vcs2.savannah.gnu.org> <6c9d91cffc1bfd801530@heytings.org> <6c9d91cffc394613f58a@heytings.org> <83eds0ksev.fsf@gnu.org> <8aadf0ddd54c85c8144a@heytings.org> <831qnhg3d9.fsf@gnu.org> <9757fbea37611e9c44b9@heytings.org> <83cz6yacxt.fsf@gnu.org> <6943e04e30e5a02a52e6@heytings.org> <838rhk5fy1.fsf@gnu.org> <6943e04e30a40824e107@heytings.org> <83k0143q37.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23592"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: 56682@debbugs.gnu.org, Gregory Heytings , monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 30 18:32:21 2023 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 1pMY0z-0005zU-1g for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 30 Jan 2023 18:32:21 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pMY0s-0004Cc-UO; Mon, 30 Jan 2023 12:32:14 -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 1pMY0i-0004Bq-C4 for bug-gnu-emacs@gnu.org; Mon, 30 Jan 2023 12:32:06 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pMY0h-0007pL-5J for bug-gnu-emacs@gnu.org; Mon, 30 Jan 2023 12:32:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pMY0h-0000tH-0H for bug-gnu-emacs@gnu.org; Mon, 30 Jan 2023 12:32:03 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 30 Jan 2023 17:32:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56682 X-GNU-PR-Package: emacs Original-Received: via spool by 56682-submit@debbugs.gnu.org id=B56682.16750998993353 (code B ref 56682); Mon, 30 Jan 2023 17:32:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 30 Jan 2023 17:31:39 +0000 Original-Received: from localhost ([127.0.0.1]:50269 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pMY0J-0000s0-6c for submit@debbugs.gnu.org; Mon, 30 Jan 2023 12:31:39 -0500 Original-Received: from relay3-d.mail.gandi.net ([217.70.183.195]:43383) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pMY0F-0000rN-0f for 56682@debbugs.gnu.org; Mon, 30 Jan 2023 12:31:35 -0500 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id 48C2860006; Mon, 30 Jan 2023 17:31:26 +0000 (UTC) In-Reply-To: <83k0143q37.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Jan 2023 19:11:08 +0200") 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:254454 Archived-At: >> > And what are your reasons for removing this? It is hard to tell whether >> > or not I agree without knowing to what I should agree ;-) >> >> The reason is that I'm now convinced that it is not a good solution to the >> problem of ill-behaving modes in the presence of long lines. > > So we are removing all the stuff that prevented font-lock from slowing > down redisplay when long lines are in the buffer? IOW, something > which we have for several months, and which so far brought up only one > complaint? Frankly, this makes no sense to me, unless we delay the > pretest for another half year or so. It's too late for such changes. > > Or am I missing something? It would be sad to lose this helpful feature, but there are too many problems with weird behavior in buffers with long-line-optimizations. For example, when there is at least one long line near the end of a diff-mode buffer, then sometimes the buffer gets truncated, 'diff-hunk-file-names' returns nil on diff headings, and there are a lot of such errors in the Messages buffer: Error during redisplay: (jit-lock-function 1) signaled (args-out-of-range # 1118 1370) ... Maybe it's still possible to fix this?