From: Yuan Fu <casouri@gmail.com>
Date: Mon, 19 Feb 2024 05:39:31 +0000 (-0800)
Subject: Don't update ranges for the whole buffer in treesit--pre-redisplay
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=c2b2144a7b2ddfef72663d24decaf47ffd3af749;p=emacs.git

Don't update ranges for the whole buffer in treesit--pre-redisplay

* lisp/treesit.el (treesit--pre-redisplay): Only update two
screen-full of text around point.

(cherry picked from commit 8f260bb93f534b24d9a93d3315804ffe0c1fec4f)
---

diff --git a/lisp/treesit.el b/lisp/treesit.el
index f811b8090bc..fa82ad898a9 100644
--- a/lisp/treesit.el
+++ b/lisp/treesit.el
@@ -1382,7 +1382,15 @@ as comment due to incomplete parse tree."
     ;; `treesit-update-ranges' will force the host language's parser to
     ;; reparse and set correct ranges for embedded parsers.  Then
     ;; `treesit-parser-root-node' will force those parsers to reparse.
-    (treesit-update-ranges)
+    (let ((len (+ (* (window-body-height) (window-body-width)) 800)))
+      ;; FIXME: As a temporary fix, this prevents Emacs from updating
+      ;; every single local parsers in the buffer every time there's an
+      ;; edit.  Moving forward, we need some way to properly track the
+      ;; regions which need update on parser ranges, like what jit-lock
+      ;; and syntax-ppss does.
+      (treesit-update-ranges
+       (max (point-min) (- (point) len))
+       (min (point-max) (+ (point) len))))
     ;; Force repase on _all_ the parsers might not be necessary, but
     ;; this is probably the most robust way.
     (dolist (parser (treesit-parser-list))