> a script to install vim plugins as ruby gems). Vimana. But you can't "load" packages at runtime of Vim. That's why I implemented a VimL only solution. Also I didn't knew Ruby that time.
ZyX also spotted the issue: What is if users prefer using stable versions (found on www.vim.org) over the git/hg/svn versions of the authors? So he added a new feature (in collaboration with me). The result is that we have different sources: a) www.vim.org b) VCS (svn,hg,git,..) Each plugin has a unique name (a key) b) is merged with a) with a policy you can configure which one of: - no vcs - prefer vcs over www.vim.org - prefer www.vim.org over vcs Because this "merge" strategy is implemented using a hook you can override and specify custom behaviour easily. In practise both versions should work. So I feel there are not enough issues out there which could make me think of more sophisticated solutions. After all we should contact authors and tell them what's going wrong unless they say "I do no longer support it - do you want to take it over?". That's my vision. Marc Weber -- You received this message from the "vim_use" 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
