-
Notifications
You must be signed in to change notification settings - Fork 27
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
Question about updating LSP output #23
Comments
I am facing the same issue. |
Yes this is how it's setup for me too. I haven't had a need for an alternative as I frantically do |
I guess i am gonna get used to the same. Thanks for the info @sharksforarms. And and huge thank you for all this config. |
Ok, good to know that's just how it works. The solution I'm using is mapping |
I'm sure there's a way using an autocmd with the |
Hi, I'm the one that raised that issue. I've been using the And also, the config that I'm using... includes this option below (from the rust-tools.nvim docs):
In my issue, you can see in the gif I uploaded that it's not refreshing the inlay hints even though I have the above config. I've updated the issue within rust-tools.nvim |
Diagnostics not updating is a rust-analyzer thing: rust-lang/rust-analyzer#3107 |
Closing for now. |
Hi, I'm using the most recommended setup, and the LSP output (like inline errors and lints) only update when I save my changes to the buffer with
:w
. Should the output should update in real time or is it only supposed to update when the changes are written with:w
? Thanks!The text was updated successfully, but these errors were encountered: