Hi Thiago! On Mo, 08 Feb 2016, Thiago Arruda wrote:
> But Vim does not have these requirements and IMO implementing the > suggested channel feature will only complicate maintenance when a > simple job control could do anything users require(let external > processes worry about system-specific differences since we only care > about stdio!). > > Another complication to keep in mind if implementing a json rpc: Vim > buffers can contain binary data, what would happen if one evals > `getline(lnum)` in such a buffer? The result would probably be invalid > json. You'd have to walk through every string returned by the json rpc > engine in order to find and escape binary data. > > As I said in a previous thread, the old job control patch has almost > everything required to make this work, it just needs to be adapted to > the current code and for a callback-based API(the old implementation > uses autocmd events). It will also have to be adapted for windows, but > there seem to be quite a few competent windows developers that > contribute to Vim(mattn) and could probably port this without trouble. > > Also, I hope you see benefit of following Neovim API: There are > already few popular plugins out there that use it with a good amount > of success(neomake, vim-go, vim-R...). > > Just my two cents. Thanks for the constructive feedback. I appreciate it, that you as the Neovim creator give feedback here. It's also appreciated, that certain bugs, which have been found when developing Neovim have at least found their way back to Vim itself (although, that communication could be improved). I can only speak for myself, but I think it would be appreciated by the Vim/Neovim user community, if the API is at least standardized, so that not every plugin writer needs to either decide whether he wants to support Vim or Neovim or has to work around the particularities in both applications. Since you seem to know both interfaces, would you be willing to contribute a patch, that will help develop a consistent interface as far as this seems feasible? Bram, since you are actually working on that part of the code, can we assume, that you would look into such a patch and help the community to have at least some kind of consistent interface for its users? I really hope, that we can find a way, to work together and specify the details of those interfaces which would gain the users a lot. So let's not have personal prejudice get in our way! (I don't want to see more of those angry discussions, as its happening currently at reddit, so let's just make the best for all users). Best, Christian -- -- 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.
