Thiago Arruda wrote: [picking out individual points to avoid trying to discuss everything at the same time]
> The reason I said we would not follow Vim is because I honestly felt > that the job proposal for Vim was a regression when compared to what > we have in Neovim(and I know many plugin developers that use it will > agree with me), but could be convinced otherwise with arguments and > examples. I wonder if you read my proposal wrong, or perhaps I didn't explain something properly. I read your response, and can only say that it's all covered in what I proposed. I think it may be caused by the notion that in NeoVim a job includes the communication with the job (over pipes), while in my proposal I separate them out. So you can have a channel in JSON mode communication to a job with a pipe. I havent seen something like that in NeoVim. But then I haven't spent much time trying to understand what NeoVim is doing. Can NeoVim use msgpack on stdout? > As I said in the previous post, yes, I'm willing to update my old > patch to Vim, possibly making changes to the API(should we reach an > agreement on it). But I need to wait Bram's response, as so far I've > had pratically no feedback from him(and one can only have so much > faith). I don't think that old patch adds much, now we already have working channels. Only the part with making channels work with stdin/stdout/stderr still needs to be done. And that code already exists in os_unix.c. MS-Windows is the most difficult (since sockets there work differently from file handles) and I thought your patch doesn't have that part. > Before I finish, let me quote something LCD said in a previous message: > > > I don't really understand what problem do channels solve, or where > > is all this heading. > > This says everything: we should focus on solving the problem rather > than simply adding new features without a proper plan. Since you were > so friendly, I will later post another message that expands my > reasoning as to why I think Vim should focus on job control (at least > for now). The whole thing I propose was to support what plugin writers were asking for. With future feature requests in mind, and combining with the existing code for netbeans. Problem with netbeans is that it uses a weird message format. I want to take that in the right direction, don't want more people to use the netbeans format. JSON appears to be the best choice. I know NeoVim uses msgpack, but I just don't like it. -- hundred-and-one symptoms of being an internet addict: 209. Your house stinks because you haven't cleaned it in a week. /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
