-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Conversation
Fixes issue #13. |
Sorry about breaking it; should have tested more before pushing. Looks like I misunderstood the
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. |
That's ok. Bugs happen.) |
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. |
I was thinking about
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. |
@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. |
Related to #13. |
Consistent behavior with the rest of Vim would be the correct answer. A " is a comment character. |
This appears closed, I'll just note that it is supported with merge of #403. |
As far as I can tell (as explained by
:help command-bar
), the only downside to this is:which shouldn't pose any problems.