I meant "folks"...:)
On Mon, Apr 7, 2014 at 2:54 PM, ping song <[email protected]> wrote: > forks: > any conclusions/progress about the discussion? > > I just got a new PC and I'd like to try one of the plugin manager way to > start my vim journey on it. > previously I only did that manually in years. > > > > On Thu, Mar 27, 2014 at 11:43 AM, Nikolay Pavlov <[email protected]>wrote: > >> >> On Mar 27, 2014 7:31 PM, "Marc Weber" <[email protected]> wrote: >> > >> > Excerpts from Nikolay Pavlov's message of Tue Mar 25 20:32:13 +0000 >> 2014: >> > > With VAM you can ask to update specific plugin only. Action "update >> all >> > > plugins for which there is a newer version available" is exactly what >> VAM >> > > does if you disallow using VCS sources (otherwise it may switch source >> > > types without notice (or with, I do not actually remember)) (updating >> VCS >> > > sources which were installed manually still works fine). >> > To be honest I don't know either. We haven't defined behaviour. >> > VAM should >> > - run git pull if a plugin directory happens to be a git repository >> > - hg update if its contains a .hg directory >> > and so on. >> > >> > Thus if you turn a .git into a .hg repository :VamUpdate plugin-name >> > should do what you want. >> >> I meant changing non-VCS to VCS, not between VCS. I know that VCS types >> won't be switched. >> >> > >> > But you're right that one final goal could be a to support fixed >> > versions & update sources. The perfect "user experience" would be >> > "choose yourself" which is why the last update I made was that >> > important: It allows passing dictionaries instead of plugin names. >> > >> > Thus Activate(['plugin-name']) can be replaced by >> > Activate([{'name': 'plugin-name', 'force-change-branch-on-update': 1 >> 'force-hash': 'xxx345'}]) >> > >> > The force-* keys are not supported yet, but are trivial to add and >> document. >> > Thus user would have full control. >> > >> > I think its more important to collaborate on the declaration than on the >> > implementation. And I even failed on a "InstallPlugin" proposal. >> > >> > Thus somebody has to step up and just "win the race" - which doesn't >> > make sense now that neobundle exists unless waiting how that turns out >> > to be ... (my view). >> > >> > 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 >> > >> > --- >> > You received this message because you are subscribed to the Google >> Groups "vim_use" 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/d/optout. >> >> -- >> -- >> 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 >> >> --- >> You received this message because you are subscribed to the Google Groups >> "vim_use" 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/d/optout. >> > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" 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/d/optout.
