Nathan Ridge

Just to make sure I understand: is there a motivation for the proposed change beyond enabling potential future changes?

Should be straightforward to implement, we already have a `clangd: Restart language server` command which stops and restarts the language server, the new command would do just the stopping part.

Filing an issue in four different places is not going to get it answered faster, it will just annoy people who are spammed with repeated email notifications.

I'm going to close this as a duplicate of the recently merged https://github.com/clangd/vscode-clangd/pull/575, since I believe that PR basically satisfies the use case described here.

Can you open the Output view, select "clangd" from the dropdown, and paste the entire output you see there?

The usual diagnostic strategy to try in a situation like this is to take the command clangd tells you it's running from the log, and try running it on the...

Interesting, so the command line version is not giving the same errors you're seeing in the editor. I wonder if the difference in versions (clangd 15 vs. clang 16) is...

> Does this mean that clangd doesn't need clang to function? Correct, clangd does not invoke a clang executable. It does use clang's libraries and some built-in headers, but those...

Could you attach the following please: * a screenshot showing the diagnostics in the Problems panel but not in the editor * [clangd logs](https://clangd.llvm.org/troubleshooting#gathering-logs) (taken with `--log=verbose`)

> In the log I see the following while I typing after the '#' > I[20:52:38.008] I[20:52:38.008] --> reply:workspace/symbol(320) 0 ms Would be interesting to see logs with `--log=verbose` so...