How attached are we to taking a port (or port/fd) as well as a filename? hga@xxxxxx 08 Aug 2019 22:32 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? John Cowan 09 Aug 2019 03:07 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? Lassi Kortela 09 Aug 2019 07:42 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? hga@xxxxxx 09 Aug 2019 12:52 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? John Cowan 09 Aug 2019 14:50 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? hga@xxxxxx 09 Aug 2019 15:28 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? John Cowan 09 Aug 2019 15:48 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? hga@xxxxxx 09 Aug 2019 16:26 UTC
Re: How attached are we to taking a port (or port/fd) as well as a filename? John Cowan 09 Aug 2019 17:48 UTC
with- and without- tty mode procedures hga@xxxxxx 15 Aug 2019 14:43 UTC
Re: with- and without- tty mode procedures John Cowan 15 Aug 2019 16:04 UTC
Re: with- and without- tty mode procedures Lassi Kortela 15 Aug 2019 16:15 UTC
Re: with- and without- tty mode procedures hga@xxxxxx 15 Aug 2019 16:38 UTC
Re: with- and without- tty mode procedures John Cowan 15 Aug 2019 17:11 UTC
Re: with- and without- tty mode procedures hga@xxxxxx 20 Aug 2019 12:53 UTC
Re: with- and without- tty mode procedures John Cowan 21 Aug 2019 22:51 UTC
Re: with- and without- tty mode procedures hga@xxxxxx 22 Aug 2019 00:46 UTC
(missing)
Re: with- and without- tty mode procedures hga@xxxxxx 24 Aug 2019 21:14 UTC

Re: with- and without- tty mode procedures Lassi Kortela 15 Aug 2019 16:15 UTC

>     I'm still thinking we should expose below these fancy procedures the
>     system calls, struct, and flags primitives they use to get and set
>     line disciplines.

The line discipline stuff won't apply to the Windows console. (Well, now
they run a Linux kernel in there, but the classic console still exists.)

For Unix, there's now:

     struct termios orig_mode;
     struct termios raw_mode;

     cfmakeraw(&raw_mode);
     tcgetattr(term_fd, &orig_mode);
     tcsetattr(term_fd, TCSAFLUSH, &raw_mode);
     // ...
     tcsetattr(term_fd, TCSAFLUSH, &orig_mode);

I have some fairly full-featured terminal stuff implementing a line
editor and fullscreen display that doesn't need any other line
discipline or ioctl stuff.

What is the worst that happend from a user's point of view in the
failure mode suggested by Harold (I didn't understand all the details)?
If it's only a couple of lost characters or screen update problem, well,
those happen on a daily basis with all terminal programs :)