The issue regarding conflicts between st-arm-clangd and the VSCode extensions "clangd" and "C/C++"

[newton_1232131]

Regarding the conflict between st-arm-clangd and the VSCode extensions "clangd" and "C/C++", I had to disable or completely remove these extensions in VSCode to use st-arm-clangd. But now I'm stuck—without them, I can't develop anything outside STM32 projects! No code navigation or intelligent recognition for other projects anymore. What a pain!

[Cartu38 OpenDev · Accepted solution]

If C/C++ extension is your preferred one to support intellisense just uninstall STM32Cube clangd contribution and here you are.

I may understand myself why promoting clangd: clangd is open source while C/C++ is Microsoft private ....

What is good to me is ST is letting us as end user the choice. Their new proposal comes with a default but we are NOT locked here ... we can elect in real what we want / like the most.

[Cartu38 OpenDev]

May add another option possibly/ let's play a bit with VSCode profiles see https://code.visualstudio.com/docs/configure/profiles

This way you can keep ST proposal as a whole as part of a dedicated profile, and your favorite stuff has part of an extra one.