Re:Neovim: input encoding and you
by ThrustVectoring on Wednesday November 05, 2014 @04:45PM
(#8564463)
Any plans for nuking vimscript?
Re:Neovim: input encoding and you
by splinterofchaos on Wednesday November 05, 2014 @06:32PM
(#8564915)
Nope. See the bottom item on the FAQ: https://github.com/neovim/neovim/wiki/FAQ#are-plugin-authors...
No, Vim plugins wouldn't work anymore. Vimscript will be transpiled to Lua under the hood, though, and other languages will be fully supported for writing plugins.
Re:Neovim: input encoding and you
by splinterofchaos on Wednesday November 05, 2014 @06:30PM
(#8564906)
They'll work just fine, by being "transpiled".
We have refactored some of the code base using modern coding standards, which makes it more hackable. Some of these systems have become more efficient by, for example, using pipes over temp files.
We accept upstream patches in order to stay on top of vim, so I hope that no one will ever not use neovim because of a feature lacking (aside from a GUI--see below).
neovim creates a socket for each instance that external programs can communicate with, allowing one to write a plugin or extension in any language, providing it has a msgpack implementation. These plugins may eventually control things like the GUIs, spell checkers, syntax analysers, allowing nvim to become more focused, like a micro-kernel.
As of right now, many people have switched without having any real problems.