4 ms·
I've read and re-read about all those many quirks a lot of times over the decades, and some of the things I understand to an extend where I know what the issue
by iforgotpassword 5y ago
I've read and re-read about all those many quirks a lot of times over the decades, and some of the things I understand to an extend where I know what the issue is when something breaks... but man, the interactions between tty/pty, terminal (emulator), shell, screen, ssh and locales still sometimes make me want to scream.
Nothing better than sshing into a random system and getting a ~ when you hit backspace.
- Shared404 5y ago> Nothing better than sshing into a random system and getting a ~ when you hit backspace. Or having the backspace print as a space, but still being registered as a backspace. That one threw me the first time I ran into that.
- ghostpepper 5y agoI regularly re-read this article myself and refer new Linux devs on our team to it. It's pretty incredible that the system of PID/SID/PGID has survived under the hood of Linux (and Unix) for this many decades.
- abnercoimbre 5y agoAnd I'm guessing you could say we're too entrenched to change it?
- simplicio 5y agoI used to think the unix way of doing this was overly baroque, till I had to figure out how a terminal emulator worked in Windows, which requires an actual instance of the windows default terminal program (con.exe I think?) be drawn on the screen. So if you want to grab the IO from a terminal program (say to make your own terminal emulator), the standard solution is to draw a windows terminal off the boundry of your monitor somewhere and scrape the text out and send it to your program.* *(I think this situation has improved somewhat in recent years with Windows Console?, but I haven't had a chance to play with that yet).