Menu

1 / 16

A Neovim config for Rust that I test like software

DEV Community: rust·Xynorash·4 days ago
#HA85iUwZ
#devtorust#devto#dev#nvim#rust
Reading 0:00
15s threshold

I write Rust in RustRover at work, and I still use JetBrains tools every day. They are the reason I wanted a certain kind of editing experience in my own terminal: errors on screen while I type, a debugger that shows real values, a test tree, an undo history that survives my own mistakes.

So I built xynovim , a Neovim config for Rust on top of LazyVim. It is a personal, independent project, not affiliated with JetBrains, and this post is the short tour.

The real config on a small demo crate. Everything in this post was recorded from it, nothing is mocked up.

Two tiers of diagnostics

rust-analyzer answers while you type, with type errors in about 0.01 to 0.15 seconds. Clippy follows about half a second later (0.56 s median): bacon-ls runs it against a hardlinked shadow of your workspace on every buffer change, so lints show up before you save.

rust-analyzer, while typing.

Each message shows its first line inline.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.