xaizek
Hi, Didn't think about such issue, thanks for pointing it out. Your suggestion makes sense, updated the branch.
I agree, a better one would be to use another file for this, but two plugin-specific files nearby is too much.
I don't think it's worth it. There aren't many things worse than backward incompatible changes in my opinion. And in this particular case source of error won't be immediately obvious....
Regarding `--`, I meant to use it as a separator like in ``` gcc -o out file.c -- anything else ``` It was past midnight and I somehow thought that...
> !clang_complete: inherit Nice, I like the syntax.
Try changing configuration to this: ``` vim let g:clang_complete_auto = 1 let g:clang_complete_copen = 1 let g:clang_library_path = '/home/work/lib/llvm/' ```
@DarkDefender, the description is similar to the issue addressed by #468.
It might need explicit argument like `-std=gnu++11`, I'm not sure whether clang defaults to GNU dialect by default.
Hard to say whether it should work and something is wrong with the plugin or there is just no such completion. In clang file I found there is only one...
> ImportError: No module named _ctypes Looks like your python is broken, this shouldn't yield errors: ``` $ python Python 2.7.11 (default, Dec 6 2015, 14:10:30) [GCC 5.2.0] on linux2...