-
-
Notifications
You must be signed in to change notification settings - Fork 22
Highlighting seems broken #45
Comments
If you have treesitter playground, you should check the tree but I am pretty sure it is due to some parsing errors (due |
The colon seems to be a problem indeed. |
@vigoux Do you think you can add those issues in the project todos ? I really like the parser and want to help and I think having a nice organized list of things would help me a lot to know from where to start. |
Yep, I can do that. |
For a quick follow up, support for colon before command has been added in commit 3b69c99 |
This should have been fixed in latest master. |
@BlueDrag0n Most built-in vim commands aren't understood by the parser yet. Most of the tab, buffer, window, and tag related commands aren't understood (like @vigoux Is this something that's on your radar? Do you think the parser should explicitly support every known built-in command or should there be a "fallback" rule that will match |
That's a good question. Unfortunately, nothing is simple with VimL, and it ended up not working at all in most cases, leading to messed up ASTs in many cases. That was a long time ago though, so it might be good to reconsider this, so that we make integration of the parser easier for the end users. |
We still miss buffer and tab related commands. |
It looks like the syntax highlighting in some parts of the file got messed up. Changing the color scheme doesn't fix it, and I've no idea if this was caused by an update or another plugin. Here are some examples:
I'm running the release Neovim version 0.6.0-1 on Linux.
The text was updated successfully, but these errors were encountered: