Hacker News new | ask | show | jobs
by bru 4232 days ago
>Think i'll spend some time this holiday setting it up, appreciated!

That's not needed. With the default config or a simple vimrc it's a drop-in replacement. Some extensions don't work yet (even Syntastic) but that should be resolved soon.
2 comments
Spiritus 4232 days ago
I have no problems running Syntastic. What are you running in to?
link
bru 4232 days ago
That was months ago actually. I just retried and it works perfectly, but it's still synchronous and blocks the UI. This is what I expect from neovim: provide me with async lint/checks.

The only ongoing works on the problem I've seen are https://github.com/scrooloose/syntastic/issues/1253 and https://github.com/benekastah/neomake, which I've not tried yet.

link
Spiritus 4232 days ago
There's a new plugin called neomake[1] which was written from scratch to take advantage of the Neovim async api. It's a young project though.

[1] https://github.com/benekastah/neomake

link
btipling 4232 days ago
> This is what I expect from neovim: provide me with async lint/checks.

It would have to be written using the new remote-plugin architecture I'd think. Plugins that were written for Vim would always be synchronous.

link
kolme 4231 days ago
Not necessarily. The original patch Tarruda tried to get merged into Vim provided asynchronous commands in pure Vimscript (through a new kind of event for autocmd).

I would guess this feature is already in NeoVim.

link
fizzbatter 4232 days ago
So you don't recommend starting fresh?
link
bru 4232 days ago
Do keep in mind that my experience is really limited: I compiled neovim and it works fine with my .vimrc & all extensions. So there's no reason to start fresh.

However there's no difference so far: Syntastic checks are still synchronous, and I should spend some time to research alternatives (e.g. http://www.reddit.com/r/neovim/comments/2m1w3k/neomake_an_as...)

link