3 ms·
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 m
by bru 12y 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 https://github.com/scrooloose/syntastic/issues/1253 and https://github.com/benekastah/neomake https://github.com/benekastah/neomake, which I've not tried yet.
- btipling 12y 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.
- kolme 12y agoNot 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.
- Spiritus 12y agoThere'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 https://github.com/benekastah/neomake