After working for ~3 months on the new Vim 8.0 async API, I can confidently say it's not good enough yet. Neovim had none of those problems.
-
If you start multiple different jobs in Vim 8, you get random "not a valid job" error and there is no way to debug it.
I wish Vim just would copy the Job API from Neovim. Neovim's Job API is way more powerful and simpler than Vim's one.
-
-
I feel that this is only you are not familiar with the vim8 job APIs. And if you find problems, you can file issue on github. :-/
-
I'll will file issue of course. I'm not against Vim8, but to be honest it's really get things right compared to NeoVim.
-
I can share my thoughts with you and show what I mean. I never rant usually, but for 3 months I've always had problems :/
-
if you filed the issues, you might be possible to get the solve earlier. Of course, this is NOT your cause, it's issue of vim.
-
https://github.com/vim/vim/issues/1242 … was the issue was fixed with https://github.com/vim/vim/pull/1245 … Happy it's resolved
End of conversation
New conversation -
-
-
I think Vim 8 job API is complex and law level than neovim job API. Because it seems job + RPC.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.