Björn Linse wrote:
> On Sunday, February 7, 2016 at 4:18:38 PM UTC+1, Bram Moolenaar wrote:
> > Now that the basic channel and job support is there, I would like to
> > invite plugin writers to give feedback. We probably need some more
> > features and/or change how things work.
> >
> > NeoVim is free to follow. It appears NeoVim's ideas about jobs and
> > channels are quite different. And it seems to be quite complicated.
>
> neovim implementation is indeed quite different as it uses libuv, and
> this difference will probably remain. But what specifically about the
> interface (that neovim exposes to plugin developer) do you think is
> too complicated? vim and neovim will likely diverge to the exact
> features supported, but it would be nice if the shared base features
> had the same interface.
I didn't spend much time on it, but I failed to see what messages are
exchanged between NeoVim and a plugin. It mentions using an API and
generating docs for that... Since the messages are binary, it's
impossible to use them without the msgpack library. Makes debugging
difficult.
--
hundred-and-one symptoms of being an internet addict:
175. You send yourself e-mail before you go to bed to remind you
what to do when you wake up.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
