Nathan Ridge
Nathan Ridge
> [Command](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#command) seems like a completely unspecified thing so we can define it with any semantic and commands but it might create future compatibility issues. I was thinking about `command`...
> Seems like a duplicate of https://reviews.llvm.org/D145843 Not an exact duplicate -- the patch implements a subset of the configuration discussed in this issue (concerning `` vs. `""` syntax specifically),...
I can reproduce this. The ingredients required to trigger this are: 1. Clangd is run with `--compile-commands-dir` 2. The specified directory contains a `compile_flags.txt` file, not a `compile_commands.json` file *...
Is `"directory"` an absolute path?
Ok, I believe that's valid according to the [compilation database spec](https://clang.llvm.org/docs/JSONCompilationDatabase.html) (the relative path in `"file"` is interpreted as being relative to `"directory"`). There may well be clangd bugs here,...
It's hard to guess what the relevant difference might be. (Direction of slashes in the `-I` flags perhaps? That's a complete guess though.) If you can share [clangd logs](https://clangd.llvm.org/troubleshooting#gathering-logs) for...
> Maybe the direction of the slash in the "-I" flag is the reason? Another possibility is the capitalization: compare ``` "-IC:\\VulkanSDK\\1.3.268.0\\include" ``` and ``` FileURI='file:///C:/VulkanSDK/1.3.268.0/Include/vulkan/vulkan_core.h' ``` Note that the...
> I've tested that the header insertion works fine if I use "Include" instead of "include". I think that makes this a case of https://github.com/clangd/clangd/issues/108 then.
Transferred to server repo as presumably what would need to change here is the Github Action to build the Mac release package, which is specified in this repo around [here](https://github.com/clangd/clangd/blob/d5998e7fce190cf2a828b02eb5165f86075ba815/.github/workflows/autobuild.yaml#L158).
> I noticed your use of `${workspaceFolder}` in the `clangd.arguments`. Does that currently work for you (minus the "merged" part)? I ask because using named workspaces in there does not....