Nathan Ridge

Could you show a log (similar to the one in the first comment) from clangd 13.0?

Ok, so with clang 13, the transferred compile command is: > /DATA/disk3/xzx/env-tiflash/sysroot/bin/clang++ [...] -c -x c++-header -std=gnu++20 -ferror-limit=0 -resource-dir=/DATA/disk3/xzx/env-tiflash/sysroot/lib/clang/13.0.0 -- /DATA/disk3/xzx/tiflash/dbms/src/Core/DecimalComparison.h Note that the path of Block.cpp after `-c` is...

> `compile command` you mean cmake command or clang command? I mean the clang command in the `compile_commands.json` entry. I'm not saying there's anything wrong with it, I'm just speculating...

Does restarting clangd (or restarting your editor) after renaming/deleting the file fix the issue?

> Is this a bug? Yes, I think this is still a valid bug. Ideally, clangd should update its index on the fly to reflect file renames and deletions. (If...

See also #1104 for another situation where clangd does not update its index properly while running, but only on restart.

Could you share [clangd logs](https://clangd.llvm.org/troubleshooting#gathering-logs) taken with `--log=verbose` in `"clangd.arguments"`? > If I try to execute that, I get: > > ``` > g++: error: unrecognized command-line option ‘--driver-mode=g++’ >...

Potential workaround [here](https://github.com/clangd/clangd/issues/1394#issuecomment-1328262744)

This is an interesting idea. I don't think vscode-clangd currently exposes any API surface meant for consumption by other vscode extensions, but I believe that sort of thing is possible...

I had in mind the second approach. I think this is more flexible, as it gives us the ability to grow the extension's public API over time as needed, rather...