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: Sat, 30 Jul 2022 11:07:52 +0000 Message-ID: <65cb7c73fd7af70741d6@heytings.org> References: <837d46mjen.fsf@gnu.org> <8a3eaeef01be5bfaa5ef@heytings.org> <05388e8d8812bfa3695d@heytings.org> <83v8rf5894.fsf@gnu.org> <65cb7c73fd4a999cca00@heytings.org> <83lesa6f3f.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="12074"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 30 13:08:11 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 1oHkKI-0002zw-Dk for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Jul 2022 13:08:10 +0200 Original-Received: from localhost ([::1]:36530 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oHkKG-0000xD-TN for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Jul 2022 07:08:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48106) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oHkKB-0000wx-2a for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 07:08:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44362) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oHkKA-0006a8-QH for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 07:08:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oHkKA-0003yU-FM for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 07:08: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: Sat, 30 Jul 2022 11:08: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.165917927615264 (code B ref 56682); Sat, 30 Jul 2022 11:08:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 30 Jul 2022 11:07:56 +0000 Original-Received: from localhost ([127.0.0.1]:34111 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHkK4-0003y7-2G for submit@debbugs.gnu.org; Sat, 30 Jul 2022 07:07:56 -0400 Original-Received: from heytings.org ([95.142.160.155]:58978) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHkK2-0003xz-8t for 56682@debbugs.gnu.org; Sat, 30 Jul 2022 07:07:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1659179273; bh=u5RY7gxxVBjx69BD8/NlpeEixIZau/ue9psIVRyn5kc=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=qS+rnBo8KzF3DrWZQwFarov2aFsc+e3zdZMiEk0GX7OpUXH/1xr0J+N/bqJOTbt1y CW2kQyXec1Sh7aV3lIRB5GKC9o+vwFvw0235dQlwQ9c3L588PNtkEDaOgrZbYofD72 vwZ/gfCwmrACX9B8P4uWfc1eI3rxbN+zttOedN33etCa3005GJmJA+HAcT8t0Ic5ef 59IRxouMPi9kHRx4YnJJE7ln0USi8vSKb+1LIhsoxWu4PlEhI3aF+DzjuWGHj3HMRp R7hVg6muHdUE2t89ROfgOO6rSPJT3J4zHRSX2qswXoDKhD9Vt3mR+6Bc1mONt93UzV ljJlBbUz2EUEQ== In-Reply-To: <83lesa6f3f.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:238251 Archived-At: >> IIUC, what Stefan suggests is the following, which seems (almost) fine >> to me. > > I fail to see the difference, sorry. Instead of doing the narrowing > from C we leave it to jit-lock, but tell it the limits to narrow to? Or > am I missing something? > TBH, I don't see a real difference either. Stefan says that "this way it's easy to later refine the mechanism", I guess because it is possible to "refine the mechanism" without recompiling Emacs. But as I said the problem is that there are other users of fontification-functions besides jit-lock-function. Could you (or Stefan) please have a look at the bytecomp.el problem I mentioned at the end of my previous post?