You can define text objects based on nodes of the grammar by adding queries in
textobjects.scm. Each capture group can be declared as inner or outer.
@attribute.inner
@attribute.outer
@function.inner
@function.outer
@class.inner
@class.outer
@conditional.inner
@conditional.outer
@loop.inner
@loop.outer
@call.inner
@call.outer
@block.inner
@block.outer
@parameter.inner
@parameter.outer
@regex.inner
@regex.outer
@comment.inner
@comment.outer
@assignment.inner
@assignment.outer
@return.inner
@return.outer
# For LaTeX frames
@frame.inner
@frame.outer
Some nodes only have one type:
@statement.outer
@scopename.inner
@number.inner
Some nodes have more captures available:
@assignment.lhs
@assignment.rhs
You don't have to update the support matrix in the README manually. It's generated by a CI job that runs on pushes to master.
Please use the query file formatter found
here.
There is a CI check that ensures all .scm files follow this format. Most times
it will be enough to run
nvim -l /path/to/nvim-treesitter/scripts/format-queries.lua /path/to/nvim-treesitter-textobjects/queries/,
assuming you have an up-to-date version of the nvim-treesitter plugin.