[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
screen's InitTTY vs cfmakeraw
From: |
Jeffrey Walton |
Subject: |
screen's InitTTY vs cfmakeraw |
Date: |
Mon, 11 Nov 2019 19:21:59 -0500 |
Hi Everyone,
I have an unrelated application that is having trouble reading from a
USR modem. Other modems are OK. When I test the USR modem with screen,
screen does not have the problem. I am trying to understand the
differences between my program and screen's startup code.
The big difference seems to be my program calls:
cfmakeraw(&tty);
tty.c_cflag |= CLOCAL;
tty.c_cflag |= CRTSCTS;
while screen uses InitTTY. There's a lot to InitTTY (and SetMode).
My first question is, is screen's terminal initialization code limited
to InitTTY? (I want to ensure I am not missing code elsewhere).
My second question is, why does screen _not_ use cfmakeraw? (I don't
have a lot of experience with terminals. I'm beginning to wonder if
cfmakeraw is the wrong tool).
Jeff
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- screen's InitTTY vs cfmakeraw,
Jeffrey Walton <=