cargo watch -x run after some saves turns the terminal into a mess.

[h4rldev]

Issue

It sometimes essentially locks the entire terminal and throws the text everywhere on save.
Might it be a conflict with the "menu" or something?

Screenshot

[passcod]

yeah, that's your program not resetting the screen gracefully on restart. try doing

cargo watch -s 'reset; cargo run'

[h4rldev]

Any way for me to implement that in my code?

[passcod]

sure, hook to sigint/ctrlc and cleanup state, or as a last resort, forcibly reset the screen. you can use the clearscreen crate for this, or your terminal manipulation library may have a facility

[h4rldev]

After looking up on this I seem to not find a way to catch the termination signal of cargo-watch and reset the screen

[h4rldev]

And my program seems to start thinking I pressed enter twice

[passcod]

You're right, I keep getting confused between the current states of cargo watch and watchexec. There's no easy way to catch that signal at the moment. If you use watchexec directly instead (a bit less nice for cargo projects), you'll get a SIGTERM by default, and can customise that too, and you can use --clear=reset as a simpler pattern than using tput reset.

[h4rldev]

Any plans to implement that for cargo-watch?

[passcod]

definitely. currently waiting for/working on:

• ignores to stabilise (ie for any more bugs to come out after the latest watchexec release)
• a fix for the startup behaviour (next priority)
• filter programs (pending a third party crate release)
• proper multi-command support (currently in review)

once the first two are done in watchexec, i'll consider it stable enough to start porting cargo watch, at which point i'll aim for cli flags feature parity.

tl;dr: not immediately but it's in sight