kadir çetinkaya

hmm, i hope you are aware that we are talking about clang**d** and not clang here. it will be created once you start your editing session (i.e. vscode starts clangd)

it likely because we don't perform expansion for "~" could you try with an absolute file like "/tmp/clangd-trace.json" ?

Yes there is, (thanks to @sam-mccall)! Before diving into that I would like to mention that this exact case you mentioned (i.e. compile_commands.json is under a folder called precisely `build`...

I am not sure if we really have FAQ-like discussions in vscode-clangd repo (can't say that I've been following thoroughly, so happy to be proven wrong). I think most of...

As @HighCommander4 mentioned there are two issues here. We can improve the second one on the clangd side, but I believe the first issue is the actual trouble and needs...

can you please share clangd logs?

Note that line breaks have been improved recently. You can give it a try by using soon-to-be-released clangd at https://prereleases.llvm.org/11.0.0/

Please provide clangd logs, preferably by passing `-log=verbose` to clangd. See http://clangd.llvm.org/troubleshooting.html#gathering-logs for details. They are most likely different symbols that somehow end up having the same label and it...

We should probably add some debouncing to file-status api on the client side.

yes that would be great. clangd (and rest of tooling) uses a [mapping file](https://github.com/llvm/llvm-project/blob/main/clang/include/clang/Tooling/Inclusions/StdSymbolMap.inc) derived from cppreference today because there are no first-hand mappings.