Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!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: <26143:Sep1811:47:4890@kramden.acf.nyu.edu>
Date: 18 Sep 90 11:47:48 GMT
References: <18996:Sep1609:58:2090@kramden.acf.nyu.edu> <13716@hydra.gatech.EDU>
Organization: IR
Lines: 19

In article <13716@hydra.gatech.EDU> gt0178a@prism.gatech.EDU (BURNS,JIM) writes:
  [ on screen's reconnect abilities ]

Two examples of things I use pty for all the time:

1. Flushing output reliably. If a program starts flooding the screen
with output, I can just break the connection. Then I come back with a
command like sess -T reconnect qf > /tmp/flood, type ^C when the flood
stops, and reconnect normally. How can screen do this? (Typing ^O isn't
reliable---it is delayed by the communications program and doesn't work
in raw mode---and loses possibly important output.)

2. Using a macro package. I have a context-sensitive, programmable
keyboard and screen macro package running around pty. It simply pipes
the input and output of pty appropriately. How can screen do this?

Have I missed some of screen's features?

---Dan