Fixes for various problems relating to treesitter interactions and upstream changes #300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix #299 as well.
When trying to view treesitter symbols (e.g. via
:TSymbols
) no results would appear in the side panel due to the treesitter nodes now being located in a subtable in the query results. Fixed via drilling down into the subtable ("local") before processing the node types.When using the (deprecated) reference request - default
<leader>gr
- there would be errors regarding nil references due to some undefined variables being used as parameters. Simply defining them wasn't sufficient either, as further down the callstack (inside treesittersparser
code) there's functions that aren't allowed to be run inside the async loop routines. I ended up taking all of that out and just callingwarmup_treesitter
directly, as the async_ref version of this command should be used anyway.I also quickly went through and replaced the rest of the direct references to
vim.loop
withvim.uv
(if available) that seemed to have been missed the first time around.