3 ms·
Well, not a serial terminal, judging by that ^c in the video! Worst thing about a slow baud rate is if you cat a big file you're gonna sit there and wait until
by Sir_Cmpwn 9y ago
Well, not a serial terminal, judging by that ^c in the video! Worst thing about a slow baud rate is if you cat a big file you're gonna sit there and wait until it finishes flushing down the pipe before your ^c makes it up.
- juliangoldsmith 9y agoI'd expect the ^C to immediately kill the connection. It sends a SIGHUP, which indicates the serial line has been disconnected. (Based on the DCD line, per Wikipedia.) Btw, nice work on sway.
- cat199 9y ago> I'd expect the ^C to immediately kill the connection. It sends a SIGHUP, which indicates the serial line has been disconnected. you're ignoring the actual line transfer of the control C up the wire from the keyboard, through various buffers and such.. not a serial guru by any means, so I could be wrong about the specifics, but if you've ever used a serial terminal, you'll know OP is correct.
- juliangoldsmith 9y agoI'd think the ^C would be transmitted by a physical disconnect, i.e. changing the state of the DCD line. The DCD disconnect should immediately trigger an interrupt, which should trigger a SIGHUP. To be fair, though, I can't say I've used a proper serial terminal.
- sjmulder 9y agoIt seems to depend on the program. cat is very quick to respond to ^C whereas in vim, less and elinks often a large amount of text is printed before ^C is echoed and takes effect, like you describe. I suppose that has to do with the size of chunks written. In reality though it's more about the trickling than actually mimicking a proper serial connection.