Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!tiamat!quintro!kts
From: kts@quintro.UUCP (Kenneth T. Smelcer)
Newsgroups: comp.sys.apollo
Subject: Re: Screen Terminal Manager
Message-ID: <362@quintro.UUCP>
Date: 25 Jun 89 15:12:36 GMT
References: <8906242219.AA08246@lnic1.hprc.uh.edu>
Reply-To: kts@quintro.UUCP (Kenneth T. Smelcer)
Organization: none
Lines: 25

In article <8906242219.AA08246@lnic1.hprc.uh.edu> wescott@LNIC1.HPRC.UH.EDU (Andrew M. Wescott) writes:
>
>I have recently come across a PD product known as Screen
>that some of you may be familiar with.  Screen is a window
>manager for remote terminals that lets users have multiple
>sessions from a vt100 through the use of pseudo terminals.
>With a simple control command you can flip back and forth
>between several full-screen windows.  Specifically Screen
>provides:
>

Screen is a great program.  I've been running screen 2.0 for a couple
months and haven't had any problems at all.  Screen 1.0 and 2.0 are
very similar, the only useful difference I've noticed is at 2.0 you
can "detach" a session from the terminal, logout, come back later
and "re-attach" the session.

One warning:  you MUST be running 10.1 to use screen.  Screen uses
TCP/IP pseudo-ttys for each window and the pre-10.1 TCP/IP release
has problems doing some types of i/o with ptys.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ken Smelcer        Quintron Corp.           quintro!kts@lll-winken 
                   Quincy,  IL              tiamat!quintro!kts@uunet