Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider renaming :Bundle to :Vundle #76

Closed
tpope opened this Issue Aug 22, 2011 · 35 comments

Comments

Projects
None yet
@tpope
Copy link

tpope commented Aug 22, 2011

So lately I've been hacking on a new plugin bundler.vim, and when it came time to wrap bundle, I was hard-pressed to come up with an alternative to :Bundle. So in the spirit of minimizing confusion, I humbly ask you to consider phasing out :Bundle in favor of :Vundle.

Note that since your :Bundle is only run at start-up, and mine is a buffer-local command, there's no actual conflict, just the potential for confusion. So if you want a long deprecation cycle, that's fine. If you're attached to :Bundle, that's fine. Just putting it out there.

By the way, I think Vundle is a cool idea, but with pathogen.vim having been designed for exactly my use case, you probably won't see me leaving it anytime soon. :)

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented Aug 22, 2011

Hey Tim, thanks for stopping by! )

Well, renaming :Bundle to :Vundle doesn't really make sense to me.
It's like if Ruby's Bundler would use something else than Gem.
DSL, you know )

On the other hand I had ppl complaining about Vundle being inconsistent in naming things...

Also forcing ppl to update their configs might not be a very good thing to do...

Possible cmd clash doesn't worry me too much, but possible conflict with vim-wizard @tpope concerns me way more 8)
So i'll definitely think on your suggestion. Definitely want to know what other Vundle users think about this...

Pathogen led to Vundle creation, so i'm not expecting anything else than keeping up the great work!

@randymorris

This comment has been minimized.

Copy link
Contributor

randymorris commented Aug 22, 2011

I am 100% for renaming to Vundle. Especially since Tim's plugin seems to interface directly to bundler, thus it makes more sense for his case.

I almost always end up typing something like :Vun<tab><tab><c-u>Bu<tab> when I try to run Vundle commands anyway..

@Taverius

This comment has been minimized.

Copy link

Taverius commented Aug 22, 2011

Well, you could be doing worse, at least you use :<PlugName><Action> for command names, makes the auto-complete useful if you don't remember the command name.

No problem with the actual renaming, V being one key away from B, on QWERTY at least ...

@tpope

This comment has been minimized.

Copy link
Author

tpope commented Aug 22, 2011

With regards to "forcing", a long deprecation cycle could mitigate that. Add :Vundle, update the docs, but leave :Bundle behind. After 6 months (or even longer if it suits you), add a deprecation warning. Assuming you rename the full family (:VundleInstall, etc), you could also add an option to disable the old commands earlier. This would have the (marginal) value of allowing one to type :Bun as a shortcut for :Bundle.

Another idea: If there's not some use case for running :Bundle interactively, you could delete it after startup. This would help to stop the monkeys that send bug reports like "Hey I started Vim in my home directory with no arguments and I can't :Bundle" from sending bug reports like "Hey I started Vim in my home directory with no arguments and it looks like there's a conflict between Vundle and bundler.vim".

autocmd VimEnter * delcommand Bundle
@jdevera

This comment has been minimized.

Copy link
Contributor

jdevera commented Aug 22, 2011

There is also the fact that the most likely user of Vundle is one who will be touching their config very often anyway. Also, Vundle is not 1.0 yet, so this is the time, if any, to break people's configs >:)

I too, go through the same process @rson described more often than not, it's already Vundle in my head.

@sparkertime

This comment has been minimized.

Copy link

sparkertime commented Aug 23, 2011

+1 to a rename. The ruby "bundler" comparison is pretty apt to me - every time I introduce someone to the joy of bundler, either they ask:

  1. "bundler install" doesn't work!
  2. "gem install bundle" doesn't work!
@marcjeanson

This comment has been minimized.

Copy link

marcjeanson commented Aug 26, 2011

I'd like to see it renamed to vundle as well. I also often start typing :VundleInstall and then correct myself.

Vundle is awesome. tpope's plugins are awesome. Vim is awesome. Thanks for all the great stuff guys.

@swaroopch

This comment has been minimized.

Copy link

swaroopch commented Aug 26, 2011

+1

@sickill

This comment has been minimized.

Copy link

sickill commented Sep 14, 2011

+1 for renaming. And great work work guys, both @gmarik and @tpope.

@beaumartinez

This comment has been minimized.

Copy link

beaumartinez commented Sep 14, 2011

Considering the plugin's name is Vundle, it makes sense to call the command Vundle (and similarly with all related commands—VundleInstall et al) as well—I'm all for the change.

@IdahoEv

This comment has been minimized.

Copy link

IdahoEv commented Oct 2, 2011

+1 as well. I am just starting to use Vundler, but thought it was very strange to have the commands "Bundle" and "BundleInstall" for a tool named "Vundler".

Otherwise, totally awesome tool and thank you for building it. This completely solves my biggest major complaint about Vim, as a new switcher from TextMate.

@houqp

This comment has been minimized.

Copy link

houqp commented Oct 8, 2011

+1 for renaming. :D

@bronson

This comment has been minimized.

Copy link

bronson commented Oct 9, 2011

Right now Vundle and vim-install-bundles use the same directives (Bundle 'tpope/bundler.vim) and can operate on the same .vimrc. FIre up either tool at any time.

Renaming :Bundle is not a problem, but it doesn't make sense for vim-install-bundles to use :Vundle. I could see both tools adopting something like Plugin tpope/bundler.vim or :Script or something.

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented Oct 9, 2011

I'm with @bronson on this!

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented Oct 9, 2011

Basically we should pick/standartize the name for what we're calling Bundle now. And it's either Plugin or Script IMO.
Renaming other :Bundle* commands to :Vundle* is fine thought.

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented Oct 9, 2011

Btw Vim-Addon-Manager uses Addon

@randymorris

This comment has been minimized.

Copy link
Contributor

randymorris commented Oct 9, 2011

If I had to choose I would choose Plugin as this seems consistent with vim's own naming (plugin, ftplugin, etc.).

I'm not very familiar with VAM, but even if you used the same name as VAM I think the syntax is very different if I recall correctly. I'm not sure consistency here is very important as they aren't currently interchangeable anyway.

@sickill

This comment has been minimized.

Copy link

sickill commented Oct 10, 2011

Agree with @rson. Syntax/usage is quite different so I don't know if it would do more good or rather more bad (confusing). Just a thought.

@rainux

This comment has been minimized.

Copy link

rainux commented Oct 23, 2011

Agree with @rson, keep consistency in different tools doesn't make much sense but introduce more confusion as side effect.

IMHO both "Bundle" and "Vundle" are good names, they both mean "a solid collection of something", but "Plugin" and "Script" both suggest "a single file". "Plugin" also confused with Vim's plugin script, a "Bundle" or "Vundle" not have to be a plugin script, e.g. it can be a color scheme.

I would suggest "Vundle" because it can means "a Vim scripts bundle", perfect explanation. And, it's a cool name, isn't it? :) But delete the "Bundle" command in VimEnter is also acceptable.

@bronson

This comment has been minimized.

Copy link

bronson commented Oct 23, 2011

Personally, I really like that vundle and vim-update-bundles can read the same vimrc. Eschew lock-in.

I agree that Script sounds like a single text file. I don't have the same thought for Plugin, seems like that could be a whole mess of files. The first sentence in :help write-local-help seems to agree.

So, I'm liking Plugin. But I agree that calling a color scheme a Plugin is a little odd.

@tpope

This comment has been minimized.

Copy link
Author

tpope commented Oct 23, 2011

Geez, you guys have just about talked me onto @gmarik's original side. Having a command named :Plugin that installs color schemes to the bundle/ directory is a step in the direction of ridiculousness.

Let me muddy the waters further by throwing in another possibilty: keep :Bundle, but switch to :VundleInstall. >:)

@sickill

This comment has been minimized.

Copy link

sickill commented Oct 23, 2011

+1 for what @tpope suggests.

@jhchabran

This comment has been minimized.

Copy link

jhchabran commented Nov 9, 2011

+1 for renaming to :Vundle*

@gmarik

This comment has been minimized.

Copy link
Contributor

gmarik commented Nov 15, 2011

@tpope

keep :Bundle, but switch to :VundleInstall. >:)

Now that's something we can go with!
Hereafter bundle is now a standard name for Vim's plugins i guess ;)

@gudezhi

This comment has been minimized.

Copy link

gudezhi commented Nov 19, 2011

+1 keep :Bundle, but switch to :VundleInstall. :D

@martinklepsch

This comment has been minimized.

Copy link

martinklepsch commented Nov 29, 2011

I think the commands should be completely changed to Vundle*.

There is no reason for a super-strict standard on this.
At the moment someone switches between "bundle-managers" he can just use:
:%s/Vundle/Bundle/ and he'd be done.

This is something you can expect from any vim user.

The suggested naming, as I understood it, will only confuse users.

@piouPiouM

This comment has been minimized.

Copy link

piouPiouM commented Mar 17, 2012

+1 for renaming to :VBundle*. It's more consistent with the plugin name.

Edit: big up :-/ Sorry, I followed the link on this page without checking the date of last comment.

@jumski

This comment has been minimized.

Copy link

jumski commented Jul 27, 2012

it is actually a real problem for me, when i source vimrc to reload some settings, i got:

Could not find task "gmarik/vundle".

Press ENTER or type command to continue
Could not find task "altercation/vim-colors-solarized".

Press ENTER or type command to continue
Could not find task "delimitMate.vim".

Press ENTER or type command to continue
Could not find task "godlygeek/tabular".

Press ENTER or type command to continue
Could not find task "kana/vim-fakeclip".

Press ENTER or type command to continue]

# ... long list of sadness for each of my vundles goes here ...

anyone know how to deal with it?
though about some conditional around whole plugin list, that runs only if vim-bundler was not loaded yet - can you guys point me to the right direction how to make it? (im not really into vimL yet...)

thanks

@ersatzryan

This comment has been minimized.

Copy link

ersatzryan commented Feb 22, 2013

👍 renaming to :Vundle

@RobertAudi

This comment has been minimized.

Copy link

RobertAudi commented Jul 17, 2013

I don't care if :Bundle gets renamed or not, but someone needs to find a solution to this problem. Right now it's impossible to use Vundle with bundler.vim and that sucks...

@teoljungberg

This comment has been minimized.

Copy link

teoljungberg commented Sep 22, 2013

I just ran into this issue today after installing vim-bundler.
I'm 👍 on the renaming :Bundle to :Vundle.
And I personally think that Vundle 'tpope/vim-bundler' is a better syntax than Bundle 'tpope/...'

@jumski

This comment has been minimized.

Copy link

jumski commented Sep 22, 2013

I've switched to https://github.com/Shougo/neobundle.vim because of this issue
NB works like a charm.

Cheers

@jvoisin

This comment has been minimized.

Copy link

jvoisin commented Sep 22, 2013

I agree too. Bundle/Vundle is confusing.

@xeorem

This comment has been minimized.

Copy link

xeorem commented Dec 20, 2013

Temporary Workaround: use a direct function call instead of the fancy Bundle syntax like this:
call vundle#config#bundle('scrooloose/nerdtree')

Instead of this:
Bundle 'scrooloose/nerdtree'

faun added a commit to faun/dotfiles that referenced this issue Feb 26, 2014

Remove vim-bundler because it conflicts w/ vundle
Both bundler.vim and vundle use :Bundle

This can cause issues. So I'm removing it.

VundleVim/Vundle.vim#76
@starcraftman

This comment has been minimized.

Copy link
Contributor

starcraftman commented Mar 23, 2014

This has been fixed with transition to a new Plugin* interface, though Bundle api remains during transition window. See PR #403 for details. I'll close this since it is very old. The old :Bundle command remains, we will phase it out after some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.