Open NotKevinOu opened 4 years ago
Error squiggles are currently disabled in "single file mode" (intentionally). It will work if you open folder, and then open the file. It's a one line change for us to re-enable the setting, but if we do that then maybe we'd want a setting to opt-in to single-file errors.
It would also be good to output better logging to explain this so users aren't confused as to why no error squiggles are appearing.
Type: LanguageService
Describe the bug
OS and Version: Windows 10 Home 1903
VS Code Version: 1.45.1
C/C++ Extension Version: 0.28.2
Other extensions you installed (and if the issue persists after disabling them): Code Runner, Gruvbox Theme, LaTeX Workshop, Remote - WSL. Issues persists after disabling all other extensions.
Does this issue involve using SSH remote to run the extension on a remote machine?: No
Description Red squiggle underlines do not appear in the editor under errors despite showing a non-zero "Error squiggle count" in the debug output. A red squiggle shows only for invalid #include statements.
Some of my settings that might be related: C_Cpp.default.enableConfigurationSquiggles: true C_Cpp.errorSquiggles: Enabled C_Cpp.intelliSenseEngine: Default C_Cpp.intelliSenseEngineFallback: Disabled
For example attached is an image where I would expect some red squiggles to be displayed. An "Error squiggle count: 2" is displayed but I cannot see the visible underling. Attached is also a copy of the debug output.
However I do see the red underlining if there is an error with an #include statement. I also see red underlining in other languages if there is an error (such as incorrect syntax in the settings.json file).
Sorry if this is a trivial issue and does not belong here. I've tried to looking through other issues and couldn't remedy this myself. I've also tried uninstalling and reinstalling VS Code, as well as uninstalling and reinstalling the C++ extension.