How to stop extension from providing error squiggles

[SirCupOfReese]

I recently switched to clangd for code completion and error squiggles in vscode and ran into an issue where I was getting error squiggles from multiple sources.

The second error squiggle is, seemingly, from clangd. The first one, however, is not. It lists the error source from GCC and will not go away even if I resolve the error. I have to manually rebuild for the error to leave, whereas the issue listed from Clang updates regularly and disappears after fixing the line.

I did some Googling and found this GitHub issue, which seems to state that CMake Tools is somehow providing error squiggles. I tried disabling the extension momentarily, and lo and behold, the clang error was the only one present. I need to keep the CMake Tools extension enabled (I guess I don't need to, but I'd really like to) but it's getting very frustrating having to rebuild to see if my error is resolved, especially since I know that the squiggles would be working correctly if CMake Tools wasn't adding lasting squiggles to the pile.

Has anyone experienced this? If not, any suggestions? I'd love to be able to use this extension.

Thank you for any help.

[gcampbell-msft]

Based on the linked GitHub issue, this should be resolved. Closing this dicussion.

If not, please feel free to open another discussion post or preferably a GitHub issue if there is a possible bug. Thanks!