News for hackers. Stuff that matters.
Re:The TTY demystified by peterwwillis on Monday June 04, 2012 @02:24PM (#4065166)
"We have already seen that a TTY device may be configured to give certain data bytes a special treatment. In the default configuration, for instance, a received ^C byte won't be handed off to the application through read(2), but will instead cause a SIGINT to be delivered to the foreground job. In a similar way, it is possible to configure the TTY to react on a stop flow byte and a start flow byte. These are typically ^S (ASCII code 19) and ^Q (ASCII code 17) respectively. Old hardware terminals transmit these bytes automatically, and expect the operating system to regulate its flow of data accordingly. This is called flow control, and it's the reason why your xterm sometimes appears to lock up when you accidentally press ^S."

A 12-year-old mystery to me is finally solved.

Re:The TTY demystified by yuhong on Monday June 04, 2012 @03:36PM (#4065512)
Remember when emacs used these as shortcuts?