Since I'm always in some sort of tmux/screen terminal, I find myself cycling through some combination of Ctrl+a q,Cntrl+q to make sure I didn't turn on flow-control (Ctrl+s).
arg flow control is the worst when trying to diagnose a frozen session. idk how many tines I've reset my network connection etc etc before realizing its gnu screen being silly (or really myself being silly)
This is why I have stty -ixon in my profile. I never use flow control anyway, not sure why I want it on.
I think we just have something against C keys. I do this to a calculator as well. It makes more sense with copying since there's absolutely no feedback that the copy was successful, but with a calculator there's no reason for it.
Ctrl+C interrupts the currently running program in a UNIX terminal, usually resulting in the program dying. That's probably what the commenter was referring to.
except usually the interrupt has visible feedback, namely returning user back to prompt or a notice that the program has caught the intercept, or if the terminal/program is hanging, ^c
I'm never calm until I see ^C
I thought they were referring to copy and pasting. There's been many times in the past I've gone to paste something and it wasn't the thing I though I just copied half a second ago. It has resulted in me abusing control + c.