5 ms·
Probably CTRL-S, which is the software XOFF flow control. If so, CTRL-Q sends XON, which will un-hang the session and resume data flow.
by orev 3y ago
Probably CTRL-S, which is the software XOFF flow control. If so, CTRL-Q sends XON, which will un-hang the session and resume data flow.
- sillysaurusx 3y agoAh yes, CTRL-Q, the most intuitive keybind for resuming a frozen terminal after pressing CTRL-S, the least likely combination to accidentally be pressed while typing.
- estebank 3y agoIt's mnemonic! [S]top and [Q]ontinue :o)
- bee_rider 3y ago[Q]ontinue was the next best option, c is already taken up to [C]ill the current process obviously.
- MenhirMike 3y agoReminds me of the game NetHack. How do you consume a potion? Well, you [q]uaff it, of course!
- layer8 3y agoThey really should have switched the latter with Verti[k]al Tab.
- bee_rider 3y agoCTRL-whatever does something funky often enough that I only hit CTRL on purpose.
- peterfirefly 3y agoStop/Qontinue.
- blueflow 3y agox & 0x1F is what the Ctrl Key used to do, with x being the other keypress. This made the ascii control characters accessible using the Control key (hence the name). So you can access Tab with Ctrl+I, the newline characters with Ctrl+J and Ctrl+M, the backspace with Ctrl+H and also XON and XOFF with Ctrl+Q and Ctrl+S.
- db48x 3y agoThey weren’t chosen with mnemonics in mind, because there are 32 of them. You might be interested in the keyboard on the IBM Model 33 teletype (<https://en.wikipedia.org/wiki/File:TTY33ASR.jpg https://en.wikipedia.org/wiki/File:TTY33ASR.jpg>) which had labels for many (but not all) control characters directly on the keycaps.
- sillysaurusx 3y agoThat’s fascinating. I’m embarrassed to have been making fun of our elder gods without even realizing it. They really were gods for creating such devices, given the constraints at the time. I doubt I could’ve done much better. The most interesting part is that we still use the same keybinds by default 60 years later. Defaults matter a great deal, but one does not expect a 60 year example. Cheers for this. Have a wonderful weekend!
- db48x 3y agoThere’s really no need to be embarrassed; we do a really poor job of teaching people these things. Honestly, it’s basically all path dependence. Features get added all the time, but we just keep layering them on top. A lot of the features that already exist are still useful, so none of them can be removed.
- hollerith 3y agoIBM was never the manufacturer of the Model 33. It was designed, made and sold by the Teletype Corporation.
- db48x 3y agoHuh, you’re right. I’ve been misremembering that for years apparently.
- makeworld 3y agoThis can be disabled.
- DonHopkins 3y agoThis has JUST started to happen to me recently a few months ago, when sshing into a server and running screen with an emacs inside. When I reconnect and restart screen back into emacs, ^S pauses output instead of doing an incremental search. I have to pop out of screen with the right escape sequence to get to the login shell I ran it in, then go "stty -ixon" to disable XON/XOFF flow control. Or always remember to do that before running "screen -RD". But I never ASKED for flow control, and it has worked PERFECTLY for decades without ever getting into +ixon mode, until just a few months ago, and now it happens every single time. Did something change recently, is ubuntu auto-installing earth shattering patches that maliciously change the default tty settings behind my back (because XON/XOFF flow control suddenly became cool again?), or did I take a walk on a foggy night and accidentally slip into an alternate universe where it's always been that way for everyone else, and I'm about to be seized by silent men in white coats and taken asylum which turns out to be a rehab clinic for people who can't read minds? https://en.wikipedia.org/wiki/All_the_Myriad_Ways https://en.wikipedia.org/wiki/All_the_Myriad_Ways I finally gave up and put an "stty -ixon" in my .bashrc, but I get the ominous feeling that's one of those tempting but dangerous kludges you're not supposed to do -- Isn't there a superstition about never touching your tty in an rc file? Or is that never touching your pp in a login file? -- that can come back and bite you in the ass later when you least expect it. It seems like this is just the latest in a long series of cascading ass bites.