Current node highlight preview functionality

[kuator]

Currently, without treesitter-unit, it's not possible to determine the syntax node the user is currently located in. This is why installing treesitter-unit becomes necessary. However, this functionality is fundamental and would be a strong candidate for inclusion as a built-in feature.

Here's a demo showcasing a potential implementation of a treewalker with highlight preview enabled:

Peek.2025-05-20.20-56.mp4

[aaronik]

Awesome - thank you for the ticket. I'm thinking on the best way forward on this now.

[aaronik]

Alright @kuator I have what probably amounts to a half fix:

Previously, if you set Treewalker's highlight_duration option to something high, and you moved around quickly, you'd see a bunch of highlights accumulating simultaneously - it kind of defeated the purpose as your whole file would look highlighted. Not a great user experience.

Now, if you set it similarly high and move around quickly, all previous highlights get removed before applying any new ones. So if you move exclusively with treewalker, this similates highlighting the node that would be swapped.

However, if you move onto a node without using treewalker, then the highlight will not be applied. This is why it's probably a half fix.

Adding a listener against all movement would add a massive performance cost to movement by just having Treewalker installed, so I don't want to do that.

And since treesitter-unit already exists and is great, I don't want to reimplement its functionality. Every new piece of functionality in Treewalker is a new piece of functionality to maintain and fix bugs against. So I think it's good to keep plugins tight and focused, doing only what they originally set out to do.

So for now this is going to have to suffice. Unless you have any other ideas!

[aaronik]

Note this is similar to #32