rust-lang / rust-lang/rust-analyzer
Errors in code doesn't show unless file is written.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Hello, I was trying to set up rust-analyzer for neovim and found out that the error messages would only appear if I write the file. E.g. when I put in some gibberish nothing would show on the side of the code telling me that this should not be here, only after I do :w would I get an error message shown. This was not the case for me when I setup C using ccls and Python with pyright. I'm using lsp-config to configure my lang servers, and have tried both rust-tools and rust-analyzer by itself, still the same behavior.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report in Neovim with rust-analyzer, comparing unsaved edits with the behavior after :w. The payload names no source files or tests; done means diagnostics appear for invalid unsaved Rust code without requiring a write, with the relevant configuration and environment recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100