-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
renderDiagnostic several issues #193
Comments
Hey 👋 Thanks for the detailed report! Fix is on the way 😄 |
Oh sweet, that was responsive! Look forward to trying this out. Btw I couldn't manage to 'get into' the render diagnostic float by calling the command twice. Not sure if that is a related or separate issue. |
Yep, I might look into implementing that if I have some more time (it would definitely be more consistent). |
Fixed with d0cec19 (version 4.0.3) |
Thanks, that's good to know! And thanks for the fix 🙏🏻 |
Neovim version (nvim -v)
v0.10.0
Operating system/version
win10 (win terminal, cmd.exe)
Output of :checkhealth rustaceanvim
How to reproduce the issue
Prepare a rust project with single main file:
From the cargo project root:
PART ONE
PART TWO (just continue, no need to restart)
Expected behaviour
PART ONE
If the naming warning should even be found by render-diagnostic then the cursor should jump to the diagnostic location and open the float window.
PART TWO
I expect the float to show the combined information about the use-after-move error
Actual behaviour
PART ONE
Float window opens, cursor moves (causing the float window to close - it flashes up for a fraction of a second).
PART TWO
Nothing happens.
The minimal config used to reproduce this issue.
The text was updated successfully, but these errors were encountered: