Support relative clangd path

My project (which has 100s of easily confused users) has a configured value for clangd.path. When I start up vscode now it prompts asking if I want to install clangd. It would be great if the extension could skip prompting if the path is valid or provide a config option to disable the prompt.

[jvilk-stripe]

Thanks for the quick fix! 😃 I was having the same issue with our vscode-clangd configuration for Sorbet; we use bazel to pull in clangd, which adds it to a subdirectory of the workspace root.

I look forward to the next version with the fix!

[sam-mccall]

For the majority of our extensions we try to make use of the ${workspaceRoot} config variable but support for that seems to be extension dependent

It’s probably best for us to support that, I’ll put together a patch ASAP (though it’s evening here and might need to get the kids to bed first!).

Also wanted to take a moment just to thank all the awesome work you guys have been doing on clangd

That’s very gracious of you, especially after we just broke everything for you. I’m glad things are working well 😃