Nathan Ridge

@GMbrianlaw that is interesting, though it has to do more with https://github.com/clangd/clangd/issues/137 than this issue (this issue is about errors in other translation units that are not open in the...

> I am also looking for a feature like this. Having the ability to run something like `$ clangd --parse-all` from the command line would be great Do you envision...

> Clangd also analyses and gives warnings/errors for code that isn't used, such as some template code that is currently not instantiated. I suspect that comes from a [clang-tidy](https://clang.llvm.org/extra/clang-tidy/) checker,...

Apologies for taking so long to get back to this. I've pushed an update to the PR which, along with [this server side patch](https://reviews.llvm.org/D143974), implement the approach discussed in [this...

Updated to address review comments. Notable changes: * Background color is now configurable * Optionally, opacity can be used instead of a background color (opacity level is also configurable)

Linking to @daiyousei-qz's patch implementing this: https://reviews.llvm.org/D127082

> Linking to @daiyousei-qz's patch implementing this: https://reviews.llvm.org/D127082 This was actually merged a while ago and will be released with clangd 16. I think the issue can be closed.

Folding of preprocessor branches is not currently implemented (https://github.com/clangd/clangd/issues/1661 is open for this). In the Linux screenshot, the lack of inactive highlight + and lack of folding on the `int...

I think this issue can be closed, as this has been implemented in https://github.com/clangd/vscode-clangd/pull/193 (requires clangd 17, since we ended up using a dedicated protocol extension for inactive regions).

> Is there an option to also disable gdb from this ms extension? I only want the gcc problem matcher. You might have more luck getting an answer to that...