Move s:viml_builtin_functions to shared file?
blueyed opened this issue ยท 10 comments
Currently s:viml_builtin_functions is defined twice in both py/pycompiler.vim (
vim-vimlparser/py/pycompiler.vim
Line 825 in edd6a79
js/jscompiler.vim.
I think this should be shared, probably in s:VimLParser.builtin_functions.
It is likely also out of date. It would be good if this could be used through some Vim function directly.
I have created vim/vim#4700 to ask about support in Vim for this.
s:VimLParser.builtin_functions
Yes, currently vimlparser doesn't have such thing.
I want to implement it for #105.
Currently scripts/update_builtin_commands.sh checks vim source (src/ex_cmds.h).
I want to provide similar script for vim functions (parse src/evalfunc.c).
Ok. As per vim/vim#4700 Vim is unlikely to provide this information itself.
However, nvim_get_commands exists already (although only for non-builtin). Might be useful in general, but only for "dynamic" linting/parsing (i.e. not for vint, vimlparser.py etc, which need the list already).
Thanks for asking to vim/vim.
I didn't know nvim_get_commands() (because I'm not neovim user).
currently neovim ex commands is updated manually. it should help auto-update ๐
Does neovim provide function list version of nvim_get_commands() ?
I don't read nvim source code, because it MAY results in license violation when I write vim patch.
(@mattn has the same policy)
I don't read nvim source code, because it MAY results in license violation when I write vim patch.
(@mattn has the same policy)
Interesting - can you elaborate?
nvim_get_commands seems to just provide the internal information: https://github.com/neovim/neovim/blob/a46fe2e615bc5f4431cad04b67ac5ba0b67ed86c/src/nvim/api/buffer.c#L653-L684
Interesting - can you elaborate?
Neovim's license is Apache license.
But Vim's license is Vim license.
I don't clearly say they are compatible.
nvim_get_commandsseems to just provide the internal information: https://github.com/neovim/neovim/blob/a46fe2e615bc5f4431cad04b67ac5ba0b67ed86c/src/nvim/api/buffer.c#L653-L684
sorry, I can't read it because of above reason ๐
I'm just afraid of that.