Rafał Chłodnicki

Yeah, you will get a complete set eventually but we can't know if the one you've received is the complete already or if you'll get it a second later. LSP...

That said, there is something I thought about now. The server could dynamically register pull diagnostics support twice, each time with a different `identifier` - see [registration options](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnosticOptions) Then the...

This was previously discussed in https://github.com/sublimelsp/LSP/issues/2572#issuecomment-2524063204 and https://github.com/rust-lang/rust-analyzer/issues/18709 and it appears to be a server spec violation (kinda, it's not explicitly stated).

Fixed by https://github.com/sublimelsp/LSP-clangd/pull/46

The closest to that you can get is by opening definition/declaration in a side-by-side view. That functionality is not bound to any key but you can find it commented out...

Closing since this is not in scope. This could be a feature request to the LSP repo itself but I don't see this happening anytime soon with the current ST...

Sometimes? So not 100% reproducible? If you can reproduce then it would help to see the LSP Logs (accessible when right clicking the panel icon in the lower-left corner)

This is likely due to us not resolving the completion BEFORE applying it. We start resolving just before applying the completion but due to ST limitations (no notifications on or...

Actually, perhaps this is a case that we can handle since it's a slightly different case. I will move it to LSP repo and treat like a bug.

My response from https://github.com/sublimelsp/LSP/pull/2633#issuecomment-3259681924: > Is there a new completion request triggered automatically when those `` are inserted? Asking because a new request would likely invalidate the data needed to...