Colen Garoutte-Carson

Taking this out of tracking, as the tracked VS issue appears to have been fixed.

Hi @aschlicht Regarding colorization; The C/C++ Extension provides colorization for semantic tokens, but syntax based colorization is provided by VS Code via it's TextMate grammar for C/C++. Given that the...

@browntarik , This seems to be an issue with use of `child_process.spawn` with a combination of an array of arguments and the `shell` option set to true. [The documentation of...

Hi @trbabb . I believe this has been addressed in 1.19.2, which is available as a prerelease in the VS Code marketplace. With 1.19.2 and a couple of minor corrections...

I don't believe this is needed. I'm not able to repro an issue from https://github.com/microsoft/vscode-cpptools/issues/11828 , and suspect that issue is user-error.

Hi @wusikijeronii . Thanks for reporting this. It appears to be related to a bug in our IntelliSense engine, which is shared with Visual Studio. I've opened an internal bug...

Hi @zhiquan114514 . Could you provide example code? Can you clarify if the issue you are seeing is due to an IntelliSense error (squiggle), or something else? I'm able to...

Hi @zhiquan114514 . That warning would appear to be coming from another extension. Problems logged by the C/C++ Extension would be indicated as `C/C++`, not `cpp`.

Hi @heshuimu . The C/C++ Extension currently supports IntelliSense modes for x86, x64, ARM, and ARM64. When an unrecognized target is encountered, it will fall back to the IntelliSense mode...

From your logs: ``` Compiler query command line: /Users/jerrymailloux/Library/Arduino15/packages/STMicroelectronics/tools/xpack-arm-none-eabi-gcc/12.2.1-1.2/bin/arm-none-eabi-g++ -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -w -std=gnu++17 -ffunction-sections -fdata-sections -fno-threadsafe-statics --param -fno-rtti -fno-exceptions ... arm-none-eabi-g++: error: unrecognized command-line option '--param=-fno-rtti' ``` >...