4 ms·
I don't know what magic combination it is but I keep hitting something on WSL2 and Windows Terminal that makes my session freeze into a blinking cursor. This r
by candiddevmike 3y ago
I don't know what magic combination it is but I keep hitting something on WSL2 and Windows Terminal that makes my session freeze into a blinking cursor. This results in me having to close the current tab and start a new terminal session completely.
We're still inventing new ways of breaking arguably the most basic user interfaces.
- _a_a_a_ 3y agocontrol-Q and control-S freeze/unfreeze the output stream (can't remember which is which). May be that?
- candiddevmike 3y agoIt doesn't seem to be that, I can't even reliability reproduce it. I originally thought it was something with the right control or right alt, but it's not consistent.
- jstanley 3y agoI keep doing this in gnome-terminal, and for years I was confused about what was going on, I thought it was a bug, but I found out what it is! It turns out there is a "read-only" mode, with some keyboard shortcut that I was triggering by accident. You just have to right click in the terminal and uncheck "read-only" to get it back.
- audidude 3y agoDunno how long it's been since you used it, but I believe keybindings for this are disabled by default now and you have to toggle them on in your profile preferences.
- orev 3y agoProbably 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.
- pjmlp 3y agoTerminals in UNIX systems are anything but basic. Windows terminal takes it to the extra level by supporting two OS terminal models. Terminals in non UNIX, that not pretend to be serial printers, like the Amiga DOS, or plain MS-DOS, those are the basic ones.
- veilrap 3y agoWindows might even support 3 if you count cmd and powershell separately :lolsob:
- jcotton42 3y agocmd and powershell are shells, not terminals.
- vidarh 3y agoThe Amiga terminal is simple in some ways, but it supports stuff most Unix terminals, won't, such as the ability to shift the text positioning by individual pixels in both x and y direction, which was of course promptly "abused" to draw bitmap graphics (exceedingly slowly) to the terminal.
- kryptiskt 3y agoMS-DOS had ANSI support with ANSI.SYS [0], that support never got into Windows NT's CMD.COM. [0]: https://en.wikipedia.org/wiki/ANSI.SYS https://en.wikipedia.org/wiki/ANSI.SYS
- pjmlp 3y agoYeah, but that is a device driver, not part of the command.com itself.
- JdeBP 3y agoYou are conflating and confusing several different things, including what operating systems even had a terminal paradigm. Windows NT started out with a "console" paradigm, like OS/2 before it, not a "terminal" one. And command processors like CMD are not what provide the "console" parts of those systems.