Nathan Ridge

One more thing to note: CLion uses a heavily patched proprietary fork of clangd. As such, behaviours and configurations that apply to CLion don't in general apply to upstream clangd.

Could you give a motivating example of a user-level feature that this would impact? Apologies if I'm being dense and it should be obvious.

We should be able to make a server change to also check for `editsNearCursor` under `capabilities.experimental`. Could you file a [server issue](https://github.com/clangd/clangd/issues/) about that?

The first thing I would suggest checking is whether the new [`BuiltinHeaders: QueryDriver`](https://clangd.llvm.org/config.html#builtinheaders) setting fixes it. Note this was added in clangd 21, so you'd need to use a snapshot...

> [@HighCommander4](https://github.com/HighCommander4) You mention manual ways of doing this on older versions. How would you do that? First, determine your compiler's built-in include path by running `/path/to/gcc -print-file-name=include`. For example,...

I don't quite understand what this issue is about. Could you please provide additional details, including: * An example code file * A description of what you're doing (in terms...

Please share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs)

> The clangd log is shown as above. That's not a log, that's a screenshot of something (the hover shown on the diagnostic I guess). Please take another look at...

The logs show that the "unknown compiler" error is coming from an `#error` directive in the file `d:/001_my_Rapier/my_Rapier/Drivers/CMSIS/Include/cmsis_compiler.h`. Could you share the contents of this file?

> [cmsis_compiler.txt](https://github.com/clangd/vscode-clangd/files/15104561/cmsis_compiler.txt) It looks like this file expects that you're using one of a specific set of compilers, and clang doesn't seem to be one of them. So, it's possible...