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#56682: Fix the long lines font locking related slowdowns Date: Tue, 16 Aug 2022 08:26:49 +0000 Message-ID: <325f95fd2bcc0b666b0b@heytings.org> References: <92da07bd02941d5537e9@heytings.org> <5308e3b5-a160-17d7-77ee-b1d00acfa20d@yandex.ru> <92da07bd02a6cc861e1a@heytings.org> <837d3lzv8n.fsf@gnu.org> <2c8d6755-cfe2-6559-3fde-3fa30ffb411e@yandex.ru> <83mtcgy44k.fsf@gnu.org> <83k07jx5jn.fsf@gnu.org> <866e510d-a060-7daa-d002-97861d056fa7@yandex.ru> <1144021660321893@iva5-64778ce1ba26.qloud-c.yandex.net> <12348081660379417@sas2-a098efd00d24.qloud-c.yandex.net> <66bbbb95983414e79637@heytings.org> <83wnb9hadb.fsf@gnu.org> <395454dd-7238-c5d0-e924-2f65a186baa7@yandex.ru> <83r11hh4pm.fsf@gnu.org> <3a1232a17b09ce88af40@heytings.org> <83edxghqg2.fsf@gnu.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="29873"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, monnier@iro.umontreal.ca, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 16 10:27:39 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 1oNrvH-0007cM-I7 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Aug 2022 10:27:39 +0200 Original-Received: from localhost ([::1]:53042 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oNrvG-0005r0-Eu for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Aug 2022 04:27:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50408) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNrug-0005ir-LH for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 04:27:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54975) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oNrug-0003uB-CM for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 04:27:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oNrug-0007Zv-5b for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 04:27: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:27: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.166063841229114 (code B ref 56682); Tue, 16 Aug 2022 08:27:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 16 Aug 2022 08:26:52 +0000 Original-Received: from localhost ([127.0.0.1]:44724 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oNruW-0007ZW-0M for submit@debbugs.gnu.org; Tue, 16 Aug 2022 04:26:52 -0400 Original-Received: from heytings.org ([95.142.160.155]:55396) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oNruU-0007ZP-Vs for 56682@debbugs.gnu.org; Tue, 16 Aug 2022 04:26:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1660638410; bh=T3/w5XNplDjJp2YCjvb8zsQJD2nHB0krU7JgzNp03vE=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=m8IaesQtyGv//Q2yC+KNQgnJFBfrH970pjekVZXUtN0ItrEqM9WbUuv0LC9BuyPdZ ZOw8g70H52tMG6L1QioFGoCs5nwTLBqKJe+/IBJ3nnWzwt7vO39t1I7L0YJvXnxSJl esfZPdAKQtGTfh6Z6dl+B3m06dmESiuaQy+t8wWBLYNy83MgdVw1kWL3QqqijLVCWA oHFWacTU5sQVoj44d9jXk4dvzd9YWHW6iTyisBuCFRJQTTksIHMJUxwfYH4yQUMIbm S/3sUzQa6mNk0Rk4YgxRxW+mDRc3b0S4H3S8VTjVpQGpnmsuF8S7fNAPBwTVXuw9Ul aNutsRBJSAkdQ== In-Reply-To: <83edxghqg2.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:239880 Archived-At: >>> No, I want a simple variable that just gives the size of the narrowed >>> region, with nil meaning don't narrow at all. >> >> FWIW, I strongly object to the addition of such a variable (unless it >> is clearly stated that it is added temporarily and should not be used >> except for testing purposes). >> >> Adding such a variable only two weeks after locked narrowing has been >> introduced means that modes will have little incentive to adapt to that >> stronger constraint, if they can "fix" whatever problems that >> constraint might cause by setting that variable to nil in their >> initialization hooks. > > Modes can do that already by changing long-line-threshold to nil, don't > they? > They can indeed, but that variable is documented as "for debugging purposes" only. Moreover setting that variable to nil implies that they deactivate all long line optimizations, which is a higher price to pay. The way I see this is that Emacs is doing efforts to solve editing slowdowns as best as possible, but that there is a "last mile" that cannot be solved without the collaboration from major and minor modes.