2013年12月29日日曜日 18時46分29秒 UTC+9 MarcWeber: > > Your repositories are great. > > > But I think to support current VAM-known repositories in neobundle is hard > > work. > > > I must write converter. I have not much time for it. > > But you have time to maintain your own plugin management system? > > In fact I don't, which is why I'd like to collaborate in the future. > > > > I've created this issue at VAM-kr to indicate that I'd like to > > collaborate. > > https://github.com/MarcWeber/vim-addon-manager-known-repositories/issues/78
OK. I commented your issue. > > > > > I think Vim needs standard plugin repositories than standard plugin > > > management system. > > > Users may use different plugin management system instead of standard. > > > But all plugin management system needs plugin repositories information. > > I agree, can we talk about how this should look like ? > OK. But I think you should create another thread like "We needs standard plugin management repository". I can join the conversation. It is not about "Completely overwrite Vim". > > > > neobundle has supports of git, svn, hg. Bazzaar and archives are not. > > > You can add the features easily. > > If you support two adding a third is trivial - which is why I don't care > > that much. Ho can we collaborate on recipes? If this means its time to > > move contentsn of VAM-kr into a online database I'm fine with such > > choice. > > > > Maybe just tell me what has been the reason to continue / start NeoBundle ? > > I'd like to understand what happened from the beginning. In the end VAM > > was started in 2009-12, NeoBundle was started in 2011-09. > I used Vundle, but I want to change the behavior completely. So I created neobundle. I didn't know about VAM in that time. I think to use VAM is too hard in Vundle user and the settings is difficult. It is like snipMate vs xptemplate problem. > > > We as community really have other problems to work on than > > duplicating recipes or "plugin managers" ? > I think "duplicate plugin managers" is OK. User should choose your own plugin manager. But "duplicate plugin information repositories" is not OK. It is useless. > > > 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.
