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.devel Subject: Re: How the long-lines "optimisation" breaks font locking. Date: Fri, 05 Aug 2022 18:30:13 +0300 Message-ID: <83o7wyzp16.fsf@gnu.org> References: <87y1w5tahv.fsf@gnus.org> <83sfmc2mph.fsf@gnu.org> <837d3n0we0.fsf@gnu.org> <71604574-d7e7-306f-bbc7-b60461737d6e@yandex.ru> <83pmhezs61.fsf@gnu.org> <12edd1f1-e073-689b-cc94-22cabca40352@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7000"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, larsi@gnus.org, emacs-devel@gnu.org, gregory@heytings.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 05 17:31:41 2022 Return-path: Envelope-to: ged-emacs-devel@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 1oJzIb-0001f9-8Y for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Aug 2022 17:31:41 +0200 Original-Received: from localhost ([::1]:45550 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oJzIa-0000Z6-0u for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Aug 2022 11:31:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59574) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJzHK-00085p-9z for emacs-devel@gnu.org; Fri, 05 Aug 2022 11:30:22 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38666) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJzHI-00014b-S6; Fri, 05 Aug 2022 11:30:20 -0400 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=wZJRGD1uqJeWeiuPmISVNxXeZ3xwl8YH2jtmEMHjLLo=; b=psnXp/hKz8An b05e6CRkpZpA4SU0Z8bLfzJQm0wZ27MNcppHGLRfi1lY9w+ed50gVxB4fLcNxZoVDO8Z61N0fcM8c aWih5sFKGgVK7vB+cujhGpUZ0wztJD6YSWFxRvTM+K+cppUVFjjBPngBD/fLtp0rGZ/aHJ5u/Hbbg h24JR56KWcq0Z+uARA22Dl8C36x33Ua5WC9lZs6dOVVRABTgmNnd1SUKSCJ3ElLqDLtA3TZ+hJXU1 i8hqgvHjZiO5h/JiQSlhsgzS9uWNYWOT/t9jrH8bFdenhtH2rvnD5TzeeWttEyQqpCNEP/4IIg6tg xvK9C8AIM+0HZx9XoP0BSg==; Original-Received: from [87.69.77.57] (port=2967 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJzHD-0007Dq-ER; Fri, 05 Aug 2022 11:30:20 -0400 In-Reply-To: <12edd1f1-e073-689b-cc94-22cabca40352@yandex.ru> (message from Dmitry Gutov on Fri, 5 Aug 2022 17:29:46 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:293120 Archived-At: > Date: Fri, 5 Aug 2022 17:29:46 +0300 > Cc: acm@muc.de, larsi@gnus.org, emacs-devel@gnu.org, gregory@heytings.org > From: Dmitry Gutov > > On 05.08.2022 17:22, Eli Zaretskii wrote: > >> Date: Fri, 5 Aug 2022 16:04:08 +0300 > >> Cc:larsi@gnus.org,emacs-devel@gnu.org,gregory@heytings.org > >> From: Dmitry Gutov > >> > >> On 05.08.2022 14:20, Eli Zaretskii wrote: > >>> Thanks. Any improvements in font-lock of any major mode is welcome. > >>> If/when enough of them get their act together, we might revisit the > >>> default value of long-line-threshold, as I already said many times. > >> As I said, changing long-line-threshold's default is not the solution > >> because this variable also determines when the fixes for the other > >> redisplay logic come into play. > >> > >> And those cause sluggishness more extensively and much earlier than > >> font-lock becomes a problem. > > That's incorrect, or at least inaccurate: part of slow redisplay is > > due to the fact that we fontify as part of displaying or as part of > > layout calculations. > > The slow part I'm referring to is not in font-lock's code, nor in CC > Mode's font-lock rules. So it can be "fixed" independently. Then where is it?