more syntax features: keycodes, special, parameters #1
Labels
enhancement
New feature or request
Comments
|
I will use this issue as tracking for missing features in the language if that's okay for you, feel free to add stuff to the original comment. |
justinmk
added a commit
to justinmk/tree-sitter-vimdoc
that referenced
this issue
Oct 5, 2022
justinmk
changed the title
justinmk
added a commit
that referenced
this issue
Jun 26, 2023
Problem:
Using _word() to define an optional arg leads to a lot of syntax errors in
real-world :help files because [brackets] are commonly used for non-args.
Solution:
Define (optional) with a regex, like (keycode) instead of using the more
"formal" mechanism. Regex has "best-effort" behavior, while seq() behaves more
strictly.
Don't treat `[{arg}]` as (optional), else it clobbers the nested `{arg}`.
fix #1
justinmk
added a commit
that referenced
this issue
Jun 26, 2023
Problem:
Using _word() to define an optional arg leads to a lot of syntax errors in
real-world :help files because [brackets] are commonly used for non-args.
Solution:
Define (optional) with a regex, like (keycode) instead of using the more
"formal" mechanism. Regex has "best-effort" behavior, while seq() behaves more
strictly.
Don't treat `[{arg}]` as (optional), else it clobbers the nested `{arg}`.
fix #1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In testing this parser for nvim-treesitter (nvim-treesitter/nvim-treesitter#2679), I noticed that some features are not yet supported, especially
{pattern}<c-o>andCTRL-O[range](that's just a bunch of literals, and so could simply be listed as anonymous nodes in the highlight query)(See https://github.com/nanotee/vimdoc-notes for the most comprehensive specification of vimdoc I've seen so far.)
The text was updated successfully, but these errors were encountered: