Hello Marc, Am Mittwoch, 29. Mai 2013 04:54:50 UTC+2 schrieb MarcWeber: > Hi Tim, > > > > I've added your solution to > > http://vim-wiki.mawercer.de/wiki/topic/vim%20plugin%20managment.html > > If you additional notes about your tools edit the page.
I made some changes. Some projects seem abandoned. The link to vim-nicktears is dead. > > > > Please learn about the > github.com/MarcWeber/vim-addon-manager-known-repositories effort. > > It tries to collect git urls and associate them with plugins found on > > www.vim.org. This page is not new to me. As far as I understand pathogen, Vundle and VAM are the most popular plugin managers. > > > > Additionally it has a way to make people aware about issues, such as > > "deprecations" when installing. > In such a case we normally just add "(deprecated, use... instead" to the package title. > > > VAM's solution has been http://vam.mawercer.de/ for windows users. > > > > If you were about adding all plugins - then you'd better introduce > > categories such as 'vim-plugins'. The package manager is also missing a > > search feature? there is search in the GUI: https://lh3.googleusercontent.com/-i50eMkvtYRE/UH2WXTucqZI/AAAAAAAAA08/kvuFu8t-SEM/s645/Npackd-1.17.4.png (see the text box named "Search"). The command line has "npackdcl search". The online list of packages is also searchable: https://npackd.appspot.com/p?q=browser&sort=created > > > > > To enable all plugins installed by Npackd it is only necessary to include > > these 2 lines in .vimrc: > > > exec ':source ' . $ALLUSERSPROFILE . > > '/Npackd/VimPlugins/vim-pathogen/autoload/pathogen.vim' > > > execute pathogen#infect($ALLUSERSPROFILE . '/Npackd/VimPlugins/{}') > > > > > > > > What do you think about it? Is this useful? > > Well - some people just use "dropbox" and manager their plugins on linux > > like operating systems. Others use cygwin or install git and move on. > > > > If we manage to package most important packages to that platform, I > > guess people will start using it - because it looks nice. > > > > I really think we should move contents from > > vim-addon-manager-known-repositories into something people can query > > easily (eg by http) - along with a way to retrieve plugins easily. > > > > Lack of time and resources :( > > > > Thus if you're looking for an automatic way to retrieve packages by .zip > > let me know. I think I can improve the interface of vam.mawercer.de with > > little effort to allow you or your users querying packages easily. > > > > I cannot imagine you wanting to maintain many packages. VAM-kr contains > > about 1200 version control urls. I didn't even notice them appearing .. > > > > ZyX has contributed at least approx 1000 of those - I've no idea how > > many of those are widely used. > > > > Marc Weber Thank you for all the information. One more question: would it be possible to use VAM instead of pathogen together with Npackd? What would be the equivalent to these commands: exec ':source ' . $ALLUSERSPROFILE . '/Npackd/VimPlugins/vim-pathogen/autoload/pathogen.vim' execute pathogen#infect($ALLUSERSPROFILE . '/Npackd/VimPlugins/{}') ? --Tim -- -- 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.
