xaizek

Do they have it documented somewhere? I just can't get how this could possibly work. Current version of clang_complete doesn't even build such invocation command for clang executable as far...

I think it's the same as #446, where wilywampa [speculated](https://github.com/Rip-Rip/clang_complete/issues/446#issuecomment-267509211) that it's due to Vim's python interface. 4.0.0 might have also broken come of the C API, but I don't...

There is no way at the moment, it's not implemented.

I doubt it's related to the plugin. I think that list that includes "everything" also appears when completion fails due to unrecoverable parsing errors. In this case something probably goes...

> Some piece of state held either in the reference to libclang or clang_complete seems like the only explanation for this behavior. libclang caches translation unit in some way and...

If it's a bug in libclang, I think it just needs to be fixed there.

Looks like a duplicate of #452. There it happened due to use of beta version of toolchain and/or OS and maybe because of youcompleteme plugin and/or wrong installation for another...

You can update to release version I guess, that is if you can. We didn't figure out why it didn't work, so I don't know workarounds.

> I think clang_complete tries to run clang from the current directory instead of the one specified in the database. That's probably a correct guess. I think #31 is about...

@graywolf is right there is no way to do it at the moment, but it's easy to implement. @boazsegev take a look at [config-inheritance branch](https://github.com/Rip-Rip/clang_complete/tree/config-inheritance). I used `clang_complete_continue` keyword, but...