Skip to content
Discussion options

You must be logged in to vote

This is indeed correct for custom textobjects with specification generated from gen_spec.treesitter() and more generally for callable specification which returns single or multiple regions. Searching for the "best" region is then done internally by 'mini.ai' based on the current reference region, search method, etc. As gen_spec.treesitter() returns an array of regions for i textobject and doesn't account for a during querying for them, the behavior you describe is indeed expected.

In theory, it is possible to update gen_spec.treesitter() querying logic to something like "search regions for both a and i textobjects, find the best (the smallest width) covering region for a, and then find th…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by echasnovski
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
question Further information is requested mini.ai
2 participants