Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!rpi!uupsi!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.questions
Subject: Re: screen program information
Message-ID: <18996:Sep1609:58:2090@kramden.acf.nyu.edu>
Date: 16 Sep 90 09:58:20 GMT
References: <24491@adm.BRL.MIL> <7598:Sep1407:49:4190@kramden.acf.nyu.edu> <1990Sep16.021433.27054@mks.com>
Organization: IR
Lines: 12

In article <1990Sep16.021433.27054@mks.com> dale@femto.mks.com (Dale Gass) writes:
> In article <7598:Sep1407:49:4190@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
    [ about screen ]
> > (Of course, this adds an unnecessary layer of communication.
> There is only one layer of communication; the screen program passing
> characters from the user's login tty, and a session's pseudo-terminal.

Sorry, you're entirely right. What I should have said was that screen's
reconnect structure unnecessarily removes a layer of flexibility: you
can't bring a screen session back into the middle of a pipe.

---Dan