vim-vimlparser
vim-vimlparser copied to clipboard
vim-jp
Vim script parser
Hi, short question. Does vimlparser support vim9 scipt yet? Asking because I see the following issue on vim-airline github actions: https://github.com/vim-airline/vim-airline/actions/runs/3635336470/jobs/6137027855 ``` Error: [vint] reported by reviewdog 🐶 E492: Not...
Hello! I went down a bit of a rabbit hole this morning. I was working on some autoload functions and decided that `echowindow` was a good logging solution. Anyway I'm...
I had originally posted this error on [the vim-language-server issue](https://github.com/iamcco/vim-language-server/issues/87), and the author of that projected directed me to vim-vmlparser. Here's my original post: **Describe the bug** I'm not sure...
https://github.com/vim-jp/vim-vimlparser/runs/4832871008 Since `master` branch is protected, to update js and py create pull-request and do auto-merging in action.
The code doesn't seem to support the falsy operator, which I actually do use in my `vimrc`. See `:h ??`.
## Example ``` ❯ cat foo.vim syn region foo start=/^ \+\|\tx/ end=/x/ ``` ## Expected behavior No parse errors, as this is valid. ## Actual behavior: ``` ❯ vint foo.vim...
Fix #117 This branch is based on #136. Please review this after #136.
Since ESM is incompatible with commonjs syntax, we cannot mix the ESM syntax in an existing file. I propose to add a new file `vimlparser.mjs` for this purpose.
Given: ```vim syn match foo +\(\\\\\|.\)\{-}[^\\]"+ ``` Results in: > t-synerror.vim:1:25:Error: EVP_E492: Not an editor command: \)\{-}[^\\]"+ It seems to mistake the (escaped) "|" for a command separator (bar) therein....
Related issue: https://github.com/vim-jp/vim-vimlparser/issues/98 Anything can be used as the pattern delimiter, and for `:syn match` the pattern is the first arg that's not recognized. This isn't anything too drastically different,...
