-
Notifications
You must be signed in to change notification settings - Fork 309
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
Quotation marks problems #270
Comments
Issue 1: I don't know if that can be fixed, will look into that. |
Code from branch 'issue270' fixes second issue, thanks! But to use this fix, I had to upgrade vim to latest version (because of missing 'pyeval' function in my old 7.3 vim). |
I'm using latest clang_complete with clang 4.0 and I'm hitting the second issue. Probably there was some regression since the time it was fixed
EDIT: I assumed that the fix was merged, turns out it is not. Maybe it is worth to consider merging it anyway? I think most vim builds are compiled with +python today |
Another solution (that doesn't require pyeval): #524 |
Hello,
I have two problems with quotation marks in cpp code, when using clang-complete:
First: when quick-fix will find warning exactly on quotation mark, inside function call, whole file after that place will be marked as string content (syntax highlighting is broken there), for example:
After that, code completion is not working anymore (until I fix the code).
Second issue: when I leave " sign alone, quick-fix will throw exception (maybe output from clang should be escaped?):
It is somehow connected with warning/error reporting.
Tested with clang-3.3-svn.
The text was updated successfully, but these errors were encountered: