> I've tried creating a summary page which we can use to collect ideas > > about what is good/bad and how to improve in the future: > > http://vim-wiki.mawercer.de/wiki/topic/neobundle-vs-vam-merge >
I think your plugin advantages are "integration with VAM-kr" contains "addon-info.json". > > > Shougo: When using vimproc and parallel processes, how do you feel about > > activation order? In some cases order does matter, do you preserve > > order ? > In install, neobundle don't care about install order. But, if plugin activation(lazy loading), is not. But it is too difficult to explain. > > > VAM does have some sophisticated implementation about preserving manual > > patches (eg running diff, updating, then applying patch) when using .zip > > archives. Did anybody ever use this feature? I think I did too much on > > this topic. > I think it is interesting feature. > > > I eventually have more use casse for async processing of trees of tasks. > > (eg tagging multiple directories) - thus does it make sense to move such > > "logic" into its own plugin? > Sorry, I don't want to do it... > > > The most important question is: Are plugin managers more important than > > fixing Vim (I mean both NeoBundle,VAM,Vundle,.. they all work reasonably > > well and don't take much of my time when getting their jobs done) > What's the "fixing Vim" means? I think plugin managers are important. But I don't know about "fixing Vim". > > > 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.
