Hi, I've written a couple of large vim plugins, I'm working with ZyX on Powerline, and I'd like to add my vote for the proposed functionality in this RFC.
Having direct access to vim functionality with good bindings like suggested in this RFC would remove a huge hurdle with writing vim plugins, and I think it would boost the plugin ecosystem and modernize vim quite a bit. The most important bindings would in my opinion be *.options, *.augroup, the ability to call vim functions directly through *.functions.*, the ability to access variables directly and the ability to access and update hlgroups directly. I also think that if any functionality from this RFC should be implemented, it should be either all or nothing. I'm already sick of having to deal with different levels of Python support in the vim 7.3 patchsets, and I'd prefer to not have to tell users to use certain patchsets to have access to certain parts of this RFC, or to have to add even more code to maintain support for different vim versions. A concern I have is: would this RFC apply similarly to other supported languages like Ruby? I think it would be unfair to add this awesome functionality to Python only, and I can imagine that doing so would create a bit of anger among developers who prefer other languages. -- -- 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/groups/opt_out.
