Ignore include errors

[aaronovz1]

How do you configure the extension to ignore the "#include errors detected" messages? I have files which are auto generated and won't be available in the workspace. This is causing a lot of spam and masking finding real issues from Flylint, etc.

[sean-mcmanus]

You can set C_Cpp.errorSquiggles to "Disabled", although that will disable all squiggles. You could also try adding the path to the generated files to your includePath.

[aaronovz1]

includePath isn't really an option as the workspace is kind of complicated. I'd rather just be able to disable this type of warning/error.

[sean-mcmanus]

So disable the missing include error, but show other errors still? Sounds similar to #1231 ...maybe another issue too.

[aaronovz1]

Yep that would be ideal. For now I've Disabled errorSquiggles to reduce the noise, but I am still seeing:
Include file not found in browse.path.

Shouldn't this check be disabled as well?

[sean-mcmanus]

Ah, there's no setting to get rid of that currently. We've had previous requests for this (not sure what issue number).

If this VS Code issue were fixed (microsoft/vscode#51103) you could filter out all problems from our extension.

You could also set C_Cpp.intelliSenseEngine to "Disabled", which will disable all language features.

[aaronovz1]

What does intelliSenseEngine control? Does disabling that essentially turn off the entire extension? I still want intellisense and autocomplete features.

[sean-mcmanus]

@aaronovz1 Yeah, it would disable all IntelliSense, autocomplete, etc....everything except the debugger.

[bobbrow]

You don't want to disable all of IntelliSense just to disable a squiggle. I'm actually not able to reproduce this problem. "C_Cpp.errorSquiggles": "Disabled" should be hiding all squiggles when the default IntelliSense is enabled.

That one you are reporting makes it sound like you're using the "Tag Parser" IntelliSense or something. What is your setting for C_Cpp.intelliSenseEngine and C_Cpp.intelliSenseEngineFallback?

[sean-mcmanus]

@bobbrow Yeah, you're right. errorSquiggles "Disabled" with intelliSenseEngine "Default" doesn't show the include error message, but it does with intelliSenseEngine "Tag Parser" (with 0.28.0). I do see the message appear briefly, but then it disappears when the squiggle update finishes -- it's possible if the squiggle update fails (i.e. from an IntelliSense process crash) then the bug might repro.

[aaronovz1]

I had to turn the "Intellisense Engine Fallback" to Disabled and this looks to have removed the remaining warnings. Output is looking good now while using the C/C++ Advanced Lint + cppcheck as the replacement.