'How to disable error squiggles in visual studio code
I am using Visual Studio Code to program in C++ but it keeps giving me error squiggles. I tried disabling them in the settings by changing C_Cpp error squiggles
to disabled
but they still appear. Is there anything else I need to do to disable them as I find them very annoying?
Solution 1:[1]
The straightforward thing works
What you said you did works for me in VSCode 1.37.1.
Before, with defaults:
Changing the setting:
After:
Excerpt of settings.json
:
{
....
"C_Cpp.errorSquiggles": "Disabled"
}
Hypotheses about why it did not work for you
There is another settings.json
attribute called C_Cpp.default.enableConfigurationSquiggles
. Might you have accidentally changed that one?
Is "C_Cpp: Intelli Sense Engine" set to "Default"? It should be (rather than "Tag Parser") in order to disable squiggles.
Maybe the syntax error you have is different somehow?
For ease of reproduction, it would help to see your settings.json
, c_cpp_properties.json
, and an example of erroneous syntax with squiggles.
Solution 2:[2]
If you are looking for a language agnostic solution, you can make the squiggly lines transparent by adding following setting to in settings file. As far as I know, there is no settings to turn the error decorations off.
"workbench.colorCustomizations": {
// ??
"editorError.foreground": "#00000000"
}
For a specific language:
"workbench.colorCustomizations": {
"[jsonc]": {
// ??
"editorError.foreground": "#00000000"
}
}
Please note that we use 8-digit hex value, the first six is not important but last two should be zero to make the color transparent.
Here is how you can do it programmatically in an extension:
workspace.getConfiguration('workbench').update( 'colorCustomizations', {
"editorError.foreground": "#00000000",
});
Solution 3:[3]
just go to command palette (ctrl + shift + P) and then search C/C++ enable error squiggles and select that. Done
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
Solution | Source |
---|---|
Solution 1 | Scott McPeak |
Solution 2 | |
Solution 3 | Syscall |