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

Allow comments after Bundle declarations #49

Merged
merged 1 commit into from
May 30, 2011
Merged

Conversation

0
Copy link
Contributor

@0 0 commented May 30, 2011

As far as I can tell (as explained by :help command-bar), the only downside to this is:

A "|" inside the command argument is not allowed then.

which shouldn't pose any problems.

@0
Copy link
Contributor Author

0 commented May 30, 2011

Fixes issue #13.

@gmarik gmarik merged commit d840b24 into VundleVim:master May 30, 2011
@gmarik
Copy link
Contributor

gmarik commented Jun 1, 2011

@0 take a look into #50
Commit's were reverted for now...
We need to update documentation to reflect that double quotes aren't allowed anymore aswell...

@0
Copy link
Contributor Author

0 commented Jun 1, 2011

Sorry about breaking it; should have tested more before pushing. Looks like I misunderstood the

Also checks for a " to start a comment.

part. It doesn't just check if a " starts a comment; it assumes " always starts a comment. As best as I can tell, the options are: disallow inline comments, but allow double quotes; or allow inline comments, but only use single quotes.

@gmarik
Copy link
Contributor

gmarik commented Jun 1, 2011

That's ok. Bugs happen.)
But we definitely need to decide on which quote to use.
Personally i'd go with single quote.
But it'll be a pain to users, as #50 has showed...
We probably need to come up with migration/deprecation or smth like that...

@0
Copy link
Contributor Author

0 commented Jun 8, 2011

Any ideas other than putting a line in the README stating the deprecation period and instructions to only use single quotes going forward? I don't know if it's at all possible to warn about double-quote usage.

@gmarik
Copy link
Contributor

gmarik commented Jun 9, 2011

I was thinking about

  • bumping Vundle's version (to 1.0 i guess) .
  • making ppl aware that double quotes no longer supported(documentation/reddit/blog/etc)

The tricky part is that vundle auto-updates itself which means that it will definitely break for those using double-quotes. So before we fully migrate to single quotes we need to come up with (as you said) a warning letting ppl know that they should update config.
Or maybe just try/catch the double quote error and show warning that they should update config...
Not sure yet, need to come up with a good solution.

@greduan
Copy link

greduan commented Dec 2, 2012

@gmarik @0 Just because this is still a topic that needs solving.

I think if we could implement some simple regex this would work. All we gotta do is check for one string, either single or double quotes, and then ignore anything after that. I don't think that should be too hard, unless you can't use regex in VimL.

@weynhamz
Copy link
Contributor

weynhamz commented Dec 2, 2012

Related to #13.

@MikeSpaceG
Copy link

Consistent behavior with the rest of Vim would be the correct answer. A " is a comment character.

@starcraftman
Copy link
Contributor

This appears closed, I'll just note that it is supported with merge of #403.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants