vim-vimlparser

vim-vimlparser copied to clipboard

Add vspec support

1

[vspec](https://github.com/kana/vim-vspec) is a vim testing tool. It uses vim syntax with [additional builtin commands](https://github.com/kana/vim-vspec/blob/1438b7987892a86e27071b4e90358367efb1cd52/doc/vspec.txt) (`describe`, `it`, `before` `after`, `context`). This adds basic support for vspec - that is, by using...

rbong

Change s:isnamec to only include colon with scope

1

Fixes https://github.com/vim-jp/vim-vimlparser/issues/79.

blueyed

[add] searchcount function

1

I add `searchcount` function in this repo. Could you check this PR?

get-me-power

Lamdas in `map` functions are cause a parsing error. For example, parsing `call map(getbufinfo(), { _, val -> 1})` generates a parsing error despite being valid VimL.

bhcleek

How can a python project depend on vimlparser?

2

I couldn't find this project uploaded to https://pypi.org/ or any setup.py / setup.cfg file for it. How can I depend on it from another python tool with the dependency properly...

dbarnett

https://github.com/vim/vim/pull/5916 [8.2.0578](https://github.com/vim/vim/commit/6c2b7b8055b96463f78abb70f58c4c6d6d4b9d55)

tyru

Run these scripts periodically using [GitHub Actions Schedule](https://help.github.com/ja/actions/reference/events-that-trigger-workflows) * scripts/update_builtin_commands.sh * scripts/update_builtin_functions.sh

tyru

Cannot use `is`, `isnot` for variable name

1

```vim let is = 42 ``` ``` vimlparser: unexpected token: is: line 75 col 5 ``` ```vim let isnot = 42 ``` ``` vimlparser: unexpected token: isnot: line 75 col...

tyru

Support :function {'<lambda>42'} ?

1

~Is this official right syntax?~ @rbtnn found it in vim help. https://github.com/vim/vim/blob/30d53e2c11e670845830bdfc29bf8c1615df61a8/runtime/doc/eval.txt#L1513

tyru

`:let` is parsed as NODE_EXCMD (not NODE_LET)

3

## Problem ```vim let ``` is parsed as ``` (excmd "let") ``` ## Expected ``` (let) ```

tyru