Nathan Ridge

Can you try ssh-ing into the server, going into the workspace directory and running `~/.vscode-server/data/User/globalStorage/llvm-vs-code-extensions.vscode-clangd/install/18.1.3/clangd_18.1.3/bin/clangd --check=some_file.cpp` (where `some_file.cpp` is a path to a source file in your workspace), and see...

> It was interesting the only arguments clangd was invoked with were the two additional ones I added in the Preferences. This part is expected. The language client does not...

I've tried to reproduce this, in both a large project I work on, and a minimal project created for the purpose, but I have not been able to so far....

@gaberundlett-tuxedo Sorry I haven't had a chance to try out your test project yet. However, I do see that you're on Windows, and we've recently had a report of a...

> Do you know if there is a good way to get the generated compile commands to have lowercase drive letters with cmake automatically? Maybe a post-build step that runs...

Looking at the code, clangd has a "compilation database search path", and it places the index at `/.cache` for the first directory `` in the search path for which `compile_commands.json`...

`clangd --check` tries to run refactorings at every source location in the file. I believe the main motivation for this is to catch crashes and debug assertions, as well as...

> Actually, what I intended was to run clangd through the command line in a CI environment to achieve consistent diagnostic output with the editor, such as those from the...

Ok, I see. So perhaps running `clangd --check` with the added option `--check-locations=false` would have the behaviour you're looking for?

> When I use clangd compiled from source code, the option `--check-locations=false` is recognized. However, when I use the binary clangd from the [release](https://github.com/clangd/clangd/releases/), it tells me that this command...