aboutsummaryrefslogtreecommitdiff
path: root/scripts/genvimvim.lua
Commit message (Collapse)AuthorAge
* vim-patch:8c1b8cb2e0b5 (#18966)Christian Clason2022-06-15
| | | | Update runtime files https://github.com/vim/vim/commit/8c1b8cb2e0b52d0853f85c2096a2f22dbc57a788
* fix(runtime/genvimvim): omit s[ubstitute] from vimCommand #18480Sean Dewar2022-05-11
| | | | | | | | | | | | | | | | | | | | It's special cased by the vimSubst syntax group, and isn't present in Vim's vimCommand group. For example, this fixes `call s:Foo()` highlighting `:` as Error in Nvim, as the `s` is parsed as vimCommand rather than as vimUserFunc since `contains=vimCommand` was added to vimUserFunc (and vimFunc) in a rt update. Interestingly, `g:`, `l:`, etc. have the same issues due to :global, :list, etc. Vim also has that problem, so it should ideally be fixed upstream. We could also omit g[lobal] from vimCommand and rely on vimGlobal instead, but it doesn't work in some cases, like when there's a `:` before the command. Also, Vim matches only `g` in vimCommand for some reason, which doesn't produce any highlight for `:global/foo/bar` (with Nvim you at least get some highlights on the `global` bit despite the leading `:`). Also, remove special handling of :py3 in syntax/vim.vim, as the generator seems to have no problems finding it.
* build(lint): check scripts/*.luaJustin M. Keyes2021-09-19
|
* Open funcs_data.mpack in binary mode. (#14944)Daniel Steinberg2021-06-30
| | | | "b" flag is required to read binary files on Windows. https://www.lua.org/pil/21.2.2.html
* vim-patch:8.1.1241: Ex command info contains confusing informationJan Edmund Lazo2021-01-01
| | | | | | | | | | | | | | | | | | | | | | Problem: Ex command info contains confusing information. Solution: When using the NOTADR flag use ADDR_OTHER for the address type. Cleanup code using NOTADR. Check for errors in create_cmdidxs.vim. Adjust Makefile to see the errors. https://github.com/vim/vim/commit/b731689e85b4153af7edc8f0a6b9f99d36d8b011 Use Lua's "assert()" to make an invalid command definition a compilation error. Misc changes: Remove 'RESTRICT' flag. Neovim does not support "restricted" mode since commit 7777532cebcfa9abc5ab2c7beae77f386feed3ca. TODO: Do not generate files before Lua assertions so that CMake always runs the generator script if the previous build has an invalid command definition.
* runtime/syntax: Fix highlighting of augroup contents (#9328)Justin M. Keyes2018-12-08
| | | | | | | | | | Comparing `vimCommand` from Vim's runtime/syntax/vim.vim, one can see that "augroup" and similar commands are conspicuously missing. They are handled specially (`vimAugroupKey`, `vimAutoCmd`). Excluding them from the generated `vimCommand` keyword list, fixes their highlighting. closes #9327
* auevents.lua: keep events in alphabetical orderJustin M. Keyes2018-10-22
|
* eval: use gperf to generate the hash of builtin functionsBjörn Linse2016-08-31
| | | | make api functions highlighted as builtins in vim.vim
* eval: Move VimL functions list to a lua fileZyX2016-08-31
| | | | | | Removes all kinds of problems with sorting, provides a ready-to-use function list representation for genvimvim.lua, does not require specifying function name twice (VimL function name (string) + f_ function name).
* release.sh: Touch NVIM_VERSION_PATCH, show obnoxious message.Justin M. Keyes2016-08-22
| | | | git-log-pretty-since.sh: fix bug
* fixup! genvimvim.lua: fix matching functionsDaniel Hahler2016-07-14
|
* genvimvim.lua: fix matching functionsDaniel Hahler2016-07-13
| | | | Fixes https://github.com/neovim/neovim/issues/5060.
* syntax: Exclude deprecated optionsZyX2015-07-26
| | | | Excluded options (compatible, edcompatible and ttyfast) are listed in vimOnlyOption group.
* syntax: List NeoVim-specific autocmd eventsZyX2015-07-26
| | | | Note: list was copied from master (7a6bf3f418c5ad94ac2ac71f21275a87d08e87b9). I did not add more events there.
* scripts: Add script which is able to generate part of vim.vim fileZyX2015-07-26
generated by cgit (git 2.34.1) at 2025-10-31 06:55:54 +0000