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: Sun, 31 Jul 2022 08:08:55 +0000 Message-ID: <8c7321f2f3400a5db9be@heytings.org> References: <837d46mjen.fsf@gnu.org> <8a3eaeef01be5bfaa5ef@heytings.org> <05388e8d8812bfa3695d@heytings.org> <83v8rf5894.fsf@gnu.org> <65cb7c73fd4a999cca00@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="3239"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, Eli Zaretskii To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jul 31 10:09:35 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 1oI411-0000gr-Bv for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 31 Jul 2022 10:09:35 +0200 Original-Received: from localhost ([::1]:38790 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oI40z-0007FB-IF for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 31 Jul 2022 04:09:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34128) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oI40V-0007Eb-GR for bug-gnu-emacs@gnu.org; Sun, 31 Jul 2022 04:09:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46585) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oI40U-0004br-7T for bug-gnu-emacs@gnu.org; Sun, 31 Jul 2022 04:09:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oI40T-0005mk-Ux for bug-gnu-emacs@gnu.org; Sun, 31 Jul 2022 04:09: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: Sun, 31 Jul 2022 08:09:01 +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.165925493822229 (code B ref 56682); Sun, 31 Jul 2022 08:09:01 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 31 Jul 2022 08:08:58 +0000 Original-Received: from localhost ([127.0.0.1]:36334 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oI40Q-0005mT-80 for submit@debbugs.gnu.org; Sun, 31 Jul 2022 04:08:58 -0400 Original-Received: from heytings.org ([95.142.160.155]:60208) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oI40O-0005mK-A1 for 56682@debbugs.gnu.org; Sun, 31 Jul 2022 04:08:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1659254935; bh=dRCT+tdsFUm3hoZTqLU5mhAJ+ovh6exFVc9nlOwlLHw=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=DMHq0aRgYThuTwbMeusO3cHVM4ANFrz1C7RF3ot3COI6X7PIsGZqdb0UKZ9eBpdF3 JuDssD8NF+9FbRyYNZV5svi5Y32JmN8v9XvJpoihje44pBd8yi6X3SyCCZ+D43ZsQL ltuEWuqYKDmFJLjGwQ0SVGUYjZzCMX6Jx+tGV3RxM00gi7U+GEdburyQ7L7WeKTK2Y 1WjPXBh+3LTgILEI7UoNlppqonmLwnZakd2Kusx3OWfjT7gbWItml5OPVQWzIIcYbX hOuUOBRtmK0SHXelm0QYPozcoERuWvf8EmCdTyrq7Q6571PsEZgd3k9mGfeEGfVFw4 rliBfnPuhEAqg== 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:238321 Archived-At: > > How 'bout we do the reverse then: set the narrowing, but let-bind a > variable to indicate that we're inside a line-length-induced narrowing, > together with the previous narrowing bounds, so jit-lock or its clients > can undo the narrowing when needed? > That's not possible: the narrowing is (really) locked (with un uninterned symbol), it cannot be undone. What would be possible would be to add an optional "unlock" argument to widen. But somehow I don't think that would be TRT, as mode authors who now do a (widen) would simply take the habit to write (widen t) instead, and the same problems would surface again. BTW, my tests show that syntax-ppss can be rather slow, when the file is large enough (say 1 GB). I didn't look at what it does, but is it not possible to design a version of syntax-ppss that would approximate, with some heuristics, what syntax-ppss does, but on a smaller chunk of the buffer? For example, I'd guess that '"' immediately followed by an alphanumeric character most likely starts a string, and '"' immediately preceded by an alphanumeric character most likely ends a string.