[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
feature/tree-sitter 1ae314dfda 1/3: ; Documentation fixes for tree-sitte
From: |
Yuan Fu |
Subject: |
feature/tree-sitter 1ae314dfda 1/3: ; Documentation fixes for tree-sitter |
Date: |
Mon, 7 Nov 2022 05:15:05 -0500 (EST) |
branch: feature/tree-sitter
commit 1ae314dfda1a7746fb31957ac3eedefd70b3c1fe
Author: Yuan Fu <casouri@gmail.com>
Commit: Yuan Fu <casouri@gmail.com>
; Documentation fixes for tree-sitter
* doc/lispref/parsing.texi (Multiple Languages): Resolve the FIXME.
---
doc/lispref/parsing.texi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/lispref/parsing.texi b/doc/lispref/parsing.texi
index a7a8f8400b..a22b088111 100644
--- a/doc/lispref/parsing.texi
+++ b/doc/lispref/parsing.texi
@@ -1335,12 +1335,12 @@ getting ranges for a parser.
Lisp programs should call @code{treesit-update-ranges} to make sure
the ranges for each parser are correct before using parsers in a
buffer, and call @code{treesit-language-at} to figure out the language
-responsible for the text at some position. Multi-language major modes
-set @code{treesit-range-settings} and
-@c FIXME: ``power''?
-@code{treesit-language-at-point-function} respectively to power these
-two functions. These functions and variables are explained in more
-detail towards the end of the section.
+responsible for the text at some position. These two functions don't
+work by themselves, they need major modes to set
+@code{treesit-range-settings} and
+@code{treesit-language-at-point-function}, which do the actual work.
+These functions and variables are explained in more detail towards the
+end of the section.
@heading Getting and setting ranges