Invalid arguments for function vundle#config#bundle

[gmile]

Somehow I am unable to use vundle at all. I've followed 2 install steps: installed vundle via git clone and edited my .vimrc (see this gist).

Am I missing something or there's a bug in vundle?

P.S. Using Vim 7.3.

[gmarik]

Hey!
that's because of the comment you use Bundle 'jpo/vim-railscasts-theme' " Railscasts theme
which is interpreted as an argument for Bundle command.

Yeah, weird...

[gmarik]

this should work

Please let me know if you have any more issues...

[gmile]

Thanks, this now seems to work. Should we close the issue?

[gmarik]

nah, let's keep it open for now, it's pretty nasty "feature"...

[gmarik]

conflicts with #50

[leifwickland]

I just bumped into this one, too. I was using the .vimrc suggested in Vundle's README.md. Deleting the comment after "Bundle 'gmarik/vundle'" worked around it.

(Thanks for making Vundle, @gmarik.)

[gmarik]

Time to make this clear in sample .vimrc, too many ppl are getting into this issue...
thanks @leifwickland )

[jasonkuhrt]

Just ran into this issue too. Fixed it in my vimrc

[vrybas]

@gmarik I guess it's time to close this issue then

[weynhamz]

@vrybas Acctually, this issue has not been solved yet.

[wakatara]

I agree with @vrybas, please for the love of god use the pull request. which allows comments on the same line. I switched over from pathogen this arvo and wasted 2 hours trying to figure out why the hell this wasn't working. Seriously, I almost reverted back to pathogen and considering this doesn't work in the example file on the home page and has behaviour which is non-standard/buggy (not allowing comment lines after the Bundle 'this/that' it is definitely an impediment to uptake. Just sayin.

[afranke]

I'd close #282 as a duplicate of this but it seems github won't let me.

[MarcWeber]

status update or close

[starcraftman]

@gmarik @jdevera If I've read this correctly, the -bar flag fixes the comment issue but breaks vimrcs if they are using double quotes on the Bundle line. Is this possible breakage the only thing holding this up?

I understand the desire to be compatible, but we can't be so paralyzed as to prevent expected behaviour no? We can add an entry to the FAQ and make a clear not in README linking to it so people fix it. If we really don't want to do that, we should just close the bug. No point leaving it open.

Note: Damn accidental deletion instead of cancel edit.

[gmarik]

The right way to solve it is to add Plugin instead of Bundle for example and enable double quotes for Plugin so it's backward compatible.

see #403

[starcraftman]

Comments are now possible using the Plugin command. The Bundle command remains unchanged due to legacy support.