Replies: 2 comments
-
Okay it seems to have fixed itself and it might related to this: rust-lang/rust-analyzer#19317 |
Beta Was this translation helpful? Give feedback.
-
[converted this to a Q&A discussion because this is unlikely to be a rustaceanvim bug] If it works in a fresh clone/checkout, then it's probably caused by local files that aren't under version control (e.g. build artefacts). Another thing that can cause rust-analyzer to hang is macros. You can try disabling certain macros in the rust-analyzer settings. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Have you read the docs and searched existing issues?
Neovim version (nvim -v)
v0.11.3
Operating system/version
MacOS 15.5
Output of :checkhealth rustaceanvim
How to reproduce the issue
I have a project where rust-analyzer hangs forever when opening it, but only when using rustaceanvim. With "normal" lsp-config rust-analyzer it works.
I have reduced the project down to a minimal example, however: If I clone the same example in a new directory it works again.
It seems like there is something about this project wich makes rustaceanvim hang forever and it also somehow remembers it, even though the problematic files should be gone.
I sadly can't share the code, since this is not a public repo.
More information:
I have attached the "minimal repro" below, which actually WORKS in my case, but only when cloned into a new directory.
Expected behaviour
NeoVim should show me hover information for println! macro.
Actual behaviour
NeoVim reports "No information available"
The minimal config used to reproduce this issue.
Beta Was this translation helpful? Give feedback.
All reactions