Open Ngoguey42 opened 2 months ago
I was able to mitigate this problem using (setq lsp-eldoc-render-all t)
It’s probably part of this PR/discussion https://github.com/emacs-lsp/lsp-mode/pull/1740, which iirc didn’t get merged because the parsing/matching was too brittle and dependant on RA unspecified implementations that could change version to version
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
Putting the cursor on a rust variable shows the type in the minibuffer:![image](https://github.com/emacs-lsp/lsp-mode/assets/9285880/417d0e1b-f652-4442-a355-190a923b1810)
Recently this stopped working correctly for some types:![image](https://github.com/emacs-lsp/lsp-mode/assets/9285880/bdd93de2-bd0a-4d0a-8a8a-c9f692fcdd81)
When I run![image](https://github.com/emacs-lsp/lsp-mode/assets/9285880/9d154a1b-55ad-46d7-a982-4effaddffa4e)
lsp-describe-thing-at-point
on this problematic type I see 2 lines:My understanding is that only the first line is shown in the minibuffer.
Steps to reproduce
cargo init --name main
to create a dummy projectopen
main.rs
with emacsanswer
i
to the prompt that offers to import the project rootAdd an
let i = 0;
line in the code.Put the cursor on
i
and witness the problem in the minibufferExpected behavior
The type of the variable should be shown
Which Language Server did you use?
emacs
GNU Emacs 29.3
RA
rust-analyzer 0.3.1932-standalone (47a901b9b 2024-04-21)
lsp-mode
OS
MacOS
Error callstack
No response
Anything else?
No response