docs(tree-sitter): add no text object found error
This commit is contained in:
parent
c1bea42fa0
commit
4e870be9ab
1 changed files with 9 additions and 0 deletions
|
@ -18,6 +18,7 @@
|
||||||
- [[#disabling-highlighting-for-certain-modes][Disabling highlighting for certain modes]]
|
- [[#disabling-highlighting-for-certain-modes][Disabling highlighting for certain modes]]
|
||||||
- [[#troubleshooting][Troubleshooting]]
|
- [[#troubleshooting][Troubleshooting]]
|
||||||
- [[#error-bad-bounding-indices-0-1][=(error "Bad bounding indices: 0, 1")=]]
|
- [[#error-bad-bounding-indices-0-1][=(error "Bad bounding indices: 0, 1")=]]
|
||||||
|
- [[#no-textobj-text-object-found][=No 'TEXTOBJ' text object found=]]
|
||||||
|
|
||||||
* Description
|
* Description
|
||||||
This module adds [[https://tree-sitter.github.io/tree-sitter/][tree-sitter]] support to doom:
|
This module adds [[https://tree-sitter.github.io/tree-sitter/][tree-sitter]] support to doom:
|
||||||
|
@ -114,3 +115,11 @@ If you only want it for certain modes then
|
||||||
This means that the text object does not have the underlying query needed, this can be
|
This means that the text object does not have the underlying query needed, this can be
|
||||||
fixed by either adding in a custom query (which would override the current key
|
fixed by either adding in a custom query (which would override the current key
|
||||||
bound.) or [[https://github.com/nvim-treesitter/nvim-treesitter-textobjects/][contributing upstream!]]
|
bound.) or [[https://github.com/nvim-treesitter/nvim-treesitter-textobjects/][contributing upstream!]]
|
||||||
|
|
||||||
|
** =No 'TEXTOBJ' text object found=
|
||||||
|
the main reason for this is the underlying text object using the =#make-range!=
|
||||||
|
predicate, which at the moment [[https://github.com/emacs-tree-sitter/elisp-tree-sitter/issues/180][is not implemented in emacs tree sitter]] (see this
|
||||||
|
issue on [[https://github.com/meain/evil-textobj-tree-sitter/issues/33][evil-textobj-tree-sitter]]).
|
||||||
|
|
||||||
|
the only way around it is to rewrite the query to not use =#make-range!= or to
|
||||||
|
implement that predicate the elisp tree sitter core
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue