Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.questions
Subject: Re: One terminal <==> many processes. How?
Message-ID: <13344@sun.uucp>
Date: Sun, 15-Feb-87 05:39:43 EST
Article-I.D.: sun.13344
Posted: Sun Feb 15 05:39:43 1987
Date-Received: Sun, 15-Feb-87 23:15:14 EST
References: <781@f103a.UUCP> <435@wvucsb.UUCP> <13319@sun.uucp> <894@epimass.UUCP>
Sender: news@sun.uucp
Reply-To: guy@sun.UUCP (Guy Harris)
Organization: Sun Microsystems, Mountain View
Lines: 15

>this version used nothing but pipes (like the first)

Which means it isn't going to understand terminal "ioctl"s, so it
won't know whether the process in question is running in cooked mode
or not.  This would drive me crazy (that's partially the reason why I
don't use EMACS windows and why I don't use "commandtool" except for
my console window); I tend to run plenty of non-cooked-mode programs
and I'd expect them to work.  (I also tend to do "su" fairly often,
and I expect *that* not to print my password.)

Yes, you can probably cook something up to do windows on a system so
depressingly vanilla that it doesn't have pseudo-ttys.  The question
is whether you'd want to use it; I know I wouldn't, but somebody out
there might find it to be such a big win that they'd be willing to
put up with the inconveniences.