Enrico Scholz

seen with emacs (lsp-mode, rustic) too. Older rust-analyzer versions return "detail" and "documentation" information in "textDocument/completion" response which are missing in 2024-10-18 E.g. ```json [Trace - 05:53:47 PM] Sending request...

or `IP_PKTINFO` + `IP6_PKTINFO`

rust-analyzer developers say in https://github.com/rust-lang/rust-analyzer/issues/18351#issuecomment-2428295678 > That sounds like the client is telling r-a it supports lazily resolving those fields, so the client needs to also send a corresponding resolve...

> Can you try to move to the next item in the completion list to see if the function detail will be displayed for the previously selected item? does not...

> The point is server can opt-in into this if it makes sense for them Sounds like a design flaw of the LSP protocol... Clients should be able to set...

> which can be significant if the language server is in remote (TRAMP) instead of local machine. this seems to make lazy-resolving yet more slower... Hundreds of resolve requests to...

> @ensc Is this solved by [rust-lang/rust-analyzer#18388](https://github.com/rust-lang/rust-analyzer/pull/18388) as stated [here](https://github.com/rust-lang/rust-analyzer/issues/18351#issuecomment-2433368697) ? With lsp-mode 20241202.334 + rust-analyzer 1.85.0-nightly (9c707a8 2024-12-07) I still see the effect from the initial report (no details...

> @ensc BTW, are you using company or corfu? company

`--ignore-local-config` (which ignores both `~/.cargo/config.toml` and `.cargo/config.toml`) would be useful when trying to create a pristine `Cargo.lock`. Atm there does not seem to exist a way to ignore `[patch]` sections...