neovim

Of course. I meant the second point. > - A way to spawn plugins through vimscript. This was fixed [here](https://github.com/tarruda/neovim/commit/acf17dbefef379ecb8e...) and will replace the initpython/initclipboard options. This alone will be enough to implement the golang proposal. This is neat. Thanks for all the work, btw, tarruda. neovim is a great project, and you deserve a lot of credit for pushing ahead with it.

> My proposal in the tracker was to allow such host-plugins to define the equivalent ex commands and viml functions instead of hardcoding them in neovim itself Defining methods via msgpack-rpc and calling through vimscript is already possible(send_call will block until the connected plugin returns a response). Here's what Neovim still needs: - A way to spawn plugins through vimscript. This was fixed [here](https://github.com/tarruda/neovim/commit/acf17dbefef379ecb8e...) and will replace the initpython/initclipboard options. This alone will be enough to implement the golang proposal. - Modify vimscript to enable definition of lower cased functions and commands, and commands that accept heredocs. This will let us move the knowledge about other languages/interpreters from the C core to vimscript, though it has the disadvantage of introducing