Ctrl+C on cargo run

[alexreg]

When I Ctrl+C on cargo run and my Rust program is set up to intercept the signal, the Cargo process stops and returns control to the terminal, even though my Rust program may still be running. I've observed this on latest nightly.

I think it would be best for cargo run to also intercept Ctrl+C when running a program, and ignore it – instead, it should just check regularly to see if the program it's running has exited. This would certainly be a more reliable approach.

[alexcrichton]

I believe this was fixed by #2818, so I'm curious, which version of Cargo were you running?

[alexreg]

The very latest.

rustc 1.14.0-nightly (cae6ab1c4 2016-11-05)

On 11 Nov 2016, at 03:23, Alex Crichton notifications@github.com wrote:

I believe this was fixed by #2818 #2818, so I'm curious, which version of Cargo were you running?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #3281 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AAEF3EWjgpHz-BaBDVCaZwGV79v_2eDdks5q89-ygaJpZM4KvUIT.

[alexcrichton]

Oh are you using rustup? If so then that's the same wrapper problem so this'd actually be a rustup bug at that point.

[alexreg]

Ah, fair point. Sorry about that. Do you know if it's already been reported for Rustup?

Sent from my iPhone

On 11 Nov 2016, at 03:32, Alex Crichton notifications@github.com wrote:

Oh are you using rustup? If so then that's the same wrapper problem so this'd actually be a rustup bug at that point.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[alexcrichton]

AFAIK no