Excerpts from ZyX ZyX's message of Wed Jun 05 00:00:31 +0200 2013: > This is the intention. Not building something into vim leads to creating > bicycles by plugin authors. And I never saw anybody using functions defined > in vim runtime files (except for vimball support in VAM). There must be a > reason for it. I think its also lack of documentation, no wiki on vim.sf.net telling people how to do things. I've made suggestion. But it looks like people don't care enough.
> There is no standard plugin manager for VimL and none at all that may > specify python dependencies. Right - Vim itself does not have a standard. there is vim huge, vim tiny, vi, .. > And it is not user who needs to care, it is developer. I bet depending on > viml plugins will not be popular at all, so no need to care. Its about legacy code. You don't to rewrite all viml code, but you may want to use PIP. I'm thinking about existing code such as indentation expressions. > > If we do - then let's have both: PIP and Vam/Vundle/etc > > But allow PIP to replace VAM. > Wondering how do you imagine this. -> future story: Provide a single place to register plugins. Then provide .zip files for Windows, and pip install archives for pip. Currently there are only about 5000 packages to supoprt. Should be doable (coutning all packages VAM-kr knows about). Then you can install everything using pip only. All which must be done is adding a setup.py file - and esuring each plugin sets rtp. Then it replaces VAM. In the long run we want such repository anyway, so tha we can search in all plugin code (whether its python, viml or something else). There may be situations where you cannot / don't want to compile vim yourself. Using a runtimepath viml soultios would be an optoin. However Vim does not allow viml to provide builtin features. builtin: lower case viml: upper case So maybe this would be another thing which could be changed. It would be nice to provide :pyx_something commands for older vim implementations. There is no way, right? Marc Weber -- -- 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.
