Nathan Ridge

One advantage of pull diagnostics is discussed in [this comment](https://github.com/microsoft/vscode-languageserver-node/issues/1678#issuecomment-3424849180). (However, note that the specific issue discussed there has an easier solution discussed at https://github.com/clangd/vscode-clangd/issues/890.)

`${workspaceFolder}` should work, its substitution is implemented [here](https://github.com/clangd/vscode-clangd/blob/e5b0022d65880bddcfbbe3381c0dc899081dad41/src/config.ts#L41). `~` is not supported but looking [further up](https://github.com/clangd/vscode-clangd/blob/e5b0022d65880bddcfbbe3381c0dc899081dad41/src/config.ts#L38) in the same function, `${userHome}` should work as an alternative.

> Hmm, but at least it doesn't expand the workspacefolder in my example when I put it in clangd.path I can't reproduce this, it seems to be expanded fine for...

> `${workspaceFolder}` works fine, but the [Variables scoped per workspace folder](https://code.visualstudio.com/docs/editor/variables-reference#_variables-scoped-per-workspace-folder) `${workspaceFolder:}` does not work. Thanks. I revised the issue title to be about this latter case.

> Examples: > #### ex1 > >  If I accept this suggestion there will be brackets after class name, but I just want the class name only In clangd...

> When I hit `f` `t` I thought clangd would match namespace `fmt` first but it didn't match it at all. When I hit `f` `t` `p` I thought clangd...

Can you share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs) please?

Not currently.

> @HighCommander4 Is there any documentation which states what are the LSP features/requests currently supported by clangd? Not at the level of individual requests. To answer this question I looked...

Thanks for filing. @travkin79 are you interested in working on this? I'm happy to provide pointers to the relevant code.