On Sunday, December 29, 2013 3:59:21 PM UTC+1, MarcWeber wrote:
> starting new thread.
>
>
>
> > 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.
>
> Why does VAM cause that impression? The doc illustrates the minimal usage:
>
>
>
> set runtimepath+=PATH-TO-VAM
>
> call vam#ActivateAddons([.. list of plugin names ..], {'auto_install' :
> 0})
>
>
>
> and that's pretty minimal.
>
I personally prefer the Vundle way. It's more clear in my vimrc and I was used
to it anyway. All bundles in one command can become messy. So NeoBundle is a
logical choice for a Vundle user who wants more options.
>
> The more complicated code just contains some additional settings and
>
> code to checkout VAM (bootstrapping it).
>
Like this?
" Load neobundle.
if isdirectory('neobundle.vim')
set runtimepath^=neobundle.vim
elseif finddir('neobundle.vim', '.;') != ''
execute 'set runtimepath^=' . finddir('neobundle.vim', '.;')
elseif &runtimepath !~ '/neobundle.vim'
if !isdirectory(s:neobundle_dir.'/neobundle.vim')
execute printf('!git clone %s://github.com/Shougo/neobundle.vim.git',
\ (exists('$http_proxy') ? 'https' : 'git'))
\ s:neobundle_dir.'/neobundle.vim'
endif
execute 'set runtimepath^=' . s:neobundle_dir.'/neobundle.vim'
endif
I got that code from Shougo's vimrc on github. Makes that you just have to copy
your vimrc and NeoBundle will be installed, which handles all other bundles. A
more convenient way to copy your complete vimsetup I can;t imagine. Only your
vimrc.
If this is what you call bootstrap then NeoBundle is a yes too in the row
bootstrap.
> Even more VAM ships with a bundle emulation:
> The emulation is not complete due to lack of time.
> So another option would be emulating NeoBundle by VAM in a similar way
It is still emulation, you can use EMACS with evil-mode too. Why emulating if
the real thing is available? You must have a good reason to emulate, like the
OS functionality of EMACS. I don't see any reason why I should prefer VAM with
NeoBundle to NeoBundle itself. NeoBundle has some advantages over VAM, which I
like. Since that are functions not avalaible in VAM it can't be emulated, like
synchronous updates. A timesaver.
I don't know about advantages of VAM over NeoBundle, maybe there should be a
page on the wiki to compare VAM and NeoBundle in details, the prons and cons of
each one. VAM and NeoBundle seem to be the most complete plugin managers.
What can NeoBundle do that VAM can't?
What can VAM do what NeoBundle can't?
What is the difference in usage?
> > I think "duplicate plugin managers" is OK.
>
> I agree - if there is a reason. Not having known about VAM is not a good
>
> reason to duplicate such a huge effort.
>
Of course that can be a good reason. Shougo probably could have known VAM
existed if he looked for it, but if you look and can't find, you will never be
sure something does not exist. With everything you program you possible are
just duplicating someone else work. And it is not just duplicating. It's
another flavour.
> > User should choose your own plugin manager.
>
> Of course. Thats' the second goal I have: Make it easier for users to
>
> choose the right tool if there are multiple choices which is why I
>
> welcome everybody to join my wiki.
That is why the focus in this thread should be on a standardizing plugin
information in one repository, which all pluginmanagers can use.
You seem not to be completely consequent. You invite everybody to your wiki,
but you also want to know why Shougo wants to continue his work on NeoBundle.
You suggest NeoBundle can be emulated by VAM. Even Vundle emulation is not
complete and VAM is missing features to be able to emulate NeoBundle. You say
you want choice, but it seems also that you want just one definite
pluginmanager, which would be VAM of course. You worked for years on it. I
understand that.
Let's focus on creating a standard plugin information pool. That most important.
One pool to rule them all. :)
Marcel Boon
--
--
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.
