procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Checkdoc fixes in treesit.el

Browse source 
* lisp/treesit.el (treesit-add-font-lock-rules)
(treesit--font-lock-mark-ranges-to-fontify): Checkdoc fixes.
This commit is contained in:
Stefan Kangas 2024-07-18 09:43:55 +02:00
parent c9d28a05d9
commit 9889774c62
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
lisp/treesit.el
View file

@ -1122,7 +1122,7 @@ and leave settings for other languages unchanged."
(t current-value)))))) (t current-value))))))
(defun treesit-add-font-lock-rules (rules &optional how feature) (defun treesit-add-font-lock-rules (rules &optional how feature)
"Add font-lock RULES to the current buffer "Add font-lock RULES to the current buffer.
RULES should be the return value of `treesit-font-lock-rules'. RULES RULES should be the return value of `treesit-font-lock-rules'. RULES
will be enabled and added to `treesit-font-lock-settings'. will be enabled and added to `treesit-font-lock-settings'.
@ -1413,7 +1413,8 @@ For RANGES and PARSER see `treesit-parser-add-notifier'.
After the parser reparses, we get the changed ranges, and After the parser reparses, we get the changed ranges, and
1) update non-primary parsers' ranges in the changed ranges 1) update non-primary parsers' ranges in the changed ranges
2) mark these ranges as to-be-fontified, 2) mark these ranges as to-be-fontified,
3) tell syntax-ppss to start reparsing from the min point of the ranges. 3) tell `syntax-ppss' to start reparsing from the min point of the
ranges.
We need to mark to-be-fontified ranges before redisplay starts working, We need to mark to-be-fontified ranges before redisplay starts working,
because sometimes the range edited by the user is not the only range because sometimes the range edited by the user is not the only range