4 ms·
Dang, I've never heard of anyone who actually _wanted_ that behavior haha, I've had so much wasted time in school projects where I thought something was running
by alexchantavy 11mo ago
Dang, I've never heard of anyone who actually _wanted_ that behavior haha, I've had so much wasted time in school projects where I thought something was running but it wasn't because I had selected text in cmd.exe haha.
- 1718627440 11mo agoIt stops running? I thought it just stops the output.
- shigawire 11mo agoIf you are waiting for the output as an indication that a task completed and you never see that output you may think the task is still running but it is actually done. Has happened to me quite a few times.
- larkost 11mo agoI am not sure that if it actually stops the program, but it does at least stop programs from printing, so for anything that gives feedback on stderr/stdout you are at least pausing the main thread. I have a mostly-non-threaded program that this happens to, and it does not continue to send messages to other systems until I un-pause it.
- jwatte 11mo agoCtrl-Z suspends the program in most UNIX shells. ("fg" to resume) Ctrl-S may or may not end up stopping the program, depending on how much it's printing, and how much output buffering there is before it blocks on writing more.