Nathan Ridge

I wrote a [proposal](https://github.com/llvm/llvm-project/issues/63565#issuecomment-1975065771) for a configuration option that would address this request among others. Feedback is welcome.

Looks like this was already on file as #514, and there's more discussion there (and more recently, also a third-party repo hosting ARM builds of clangd)

> Is there a way to convince Clangd that `` also provides the unqualified type names? It's worth trying a weekly snapshot of clangd 17 from https://github.com/clangd/clangd/releases, because it looks...

> it looks to me like https://reviews.llvm.org/D143214 may have fixed this (though I wasn't able to verify this because for me, clangd 15 already behaves the way you'd like) (My...

> closing this one as there's not much we can do on the clangd side and this has been reported in [llvm/llvm-project#60151](https://github.com/llvm/llvm-project/issues/60151) and [llvm/llvm-project#48863](https://github.com/llvm/llvm-project/issues/48863) already Maybe we can work around...

> > We already decide to parse the file in a certain language mode, based on the compile command and such. > > Surely we can do that inside ParsedAST,...

For folks following this issue, this should hopefully be fixed now in https://github.com/llvm/llvm-project/pull/84133.

The symlink path `/home/ninokett` must be leaking in from somewhere. Maybe an `-I` path in one of the compile commands? Looking in the logs for the first occurrence of `/home/ninokett`...

Having read through the discussion here, I have a few questions: @sam-mccall: The [PR](https://github.com/clangd/vscode-clangd/pull/398) you wrote and linked to above is approved. Is it ready to be merged, or is...

> > @wtdcode that is a different issue and I don't think one we can do anything about it, please file a bug against vscode. > > I have https://github.com/clangd/vscode-clangd/pull/398/files...