Colen Garoutte-Carson

Hi @CookiePLMonster With those repro steps, if I remove the `compilerPath` entry in the generated `c_cpp_properties.json`, everything appears to work as expected. The issue would seem to be that, with...

> would setting the path to "" not be preferable That would result in no IntelliSense for files not found in `compile_commands.json`. Assuming that all of the `compile_commands.json` entries are...

Hi @CookiePLMonster . > No Intellisense at all or just not querying the compiler for defines You're correct in that the IntelliSense engine would still provide results, but system headers...

>I think the original intention was for compilerPath to override only the compiler and not the arguments in compile_commands.json. Though, instead of adjusting that behavior, I'd like to use this...

This should be addressed in 1.19.4.

Hi @ghuser404 I believe this behavior is coming from VS Code, not the C/C++ Extension. The extension registers 'providers' for these operations, but VS Code decides when to invoke them....

I believe that commenter was mistaken. Extensions override defaults using a `configurationDefaults` section in their `package.json`. Ours does not contain overrides for anything under `editor.gotoLocation`, nor do I see any...

This should be addressed in 1.19.4.

I believe this may be addressed in 1.19.3. If I understand correctly, there are two issues that may be related: 1. When a `compilerPath` is specified, it should override the...

This should be addressed in 1.19.4. If you're still seeing an issue with >=1.19.4, let us know.