News for hackers. Stuff that matters.
Re:Neovim: input encoding and you by coherentpony on Wednesday November 05, 2014 @01:15PM (#8563236)
As a user, what benefit do I have switching from vim to neovim?
Re:Neovim: input encoding and you by splinterofchaos on Wednesday November 05, 2014 @03:21PM (#8564035)
The most popular neovim feature (based on reddit's reactions) seems to be job control, although not enough people are using it. You can start an asynchronous job via `jobstart('name', 'prog', ['arg'...])` which will return a job id. You can send data to the job via `jobsend(id, 'text'). Every time the program has some output available, it will trigger an autocmd to let you process it. (This happens synchronously.)

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.

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)
Re:Neovim: input encoding and you by wal0 on Wednesday November 05, 2014 @05:03PM (#8564549)
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".
Re:Neovim: input encoding and you by ebiester on Wednesday November 05, 2014 @01:21PM (#8563283)
Nothing yet. It's not ready. Eventually, better plugins and GUIs without losing what makes vim so productive.
Re:Neovim: input encoding and you by coherentpony on Wednesday November 05, 2014 @01:26PM (#8563315)
Cool, thanks.
Re:Neovim: input encoding and you by iamartnez on Wednesday November 05, 2014 @02:11PM (#8563602)
My understanding is that Neovim will make it much easier for plugins to execute tasks in parallel and in the background.

I'd use that for running ctags on save without blocking the editor, for example.

Re:Neovim: input encoding and you by riffraff on Wednesday November 05, 2014 @03:47PM (#8564138)
The reason I'm following neovim is that I'm hoping for a future where linting doesn't freeze my editor on save. Sadly,

I do like my gui, so I'll have to wait a bit more

Re:Neovim: input encoding and you by lorenzfx on Wednesday November 05, 2014 @02:56PM (#8563901)
like this new Floobits plugin [0]

[0] https://news.ycombinator.com/item?id=8559146

Re:Neovim: input encoding and you by wffurr on Wednesday November 05, 2014 @02:21PM (#8563681)
A plugin like eclim would benefit greatly from the new multi-process model.