You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm writing Rust code, sometimes helix won't write the file after I run :w or even :w!
This happens mostly when I'm running cargo run, which locks the LSP
In the bottom, I can see filepath/filename [+] after running :w, and sometimes it shows Async job failed and the file doesn't save.
This is very annoying because I assume that after :w the file has been saved so I start compiling again, just to learn that the file didn't change at all.
Reproduction Steps
I tried this:
Run hx with rust-analyzer installed
Add some dependencies to your project so that the cargo run command will take a little while to run
Write someting to main.rs and run :w
I expected this to happen:
The file would be saved right after I ran the command
Instead, this happened:
The file gets stuck in a [+] state due to (I think) the LSP being stuck since cargo run is locking it.
Summary
When I'm writing Rust code, sometimes helix won't write the file after I run
:w
or even:w!
This happens mostly when I'm running
cargo run
, which locks the LSPIn the bottom, I can see
filepath/filename [+]
after running:w
, and sometimes it showsAsync job failed
and the file doesn't save.This is very annoying because I assume that after
:w
the file has been saved so I start compiling again, just to learn that the file didn't change at all.Reproduction Steps
I tried this:
hx
withrust-analyzer
installedcargo run
command will take a little while to runmain.rs
and run:w
I expected this to happen:
The file would be saved right after I ran the command
Instead, this happened:
The file gets stuck in a
[+]
state due to (I think) the LSP being stuck sincecargo run
is locking it.Helix log
~/.cache/helix/helix.log
Platform
Linux
Terminal Emulator
foot
Installation Method
Alpine packages
Helix Version
helix 23.10
The text was updated successfully, but these errors were encountered: