🚀 go-pugleaf

while using the screen command, I see a particular problem upon which
I would like comment .

Let's say that, due to a typo, I do something dumb like
fgrep a /etc/aliases
in a screen window.  This results in a) a lot of output and b)
me realizing immediately that I did something dumb.

An even dumber thing that can happen is that I write a shell or
C which loops forever outputting text.

The problem comes when I try to either ^C the window or kill the window.
It APPEARS to me that sending requests to the screen command results
in things queued up UNTIL OUTPUT CEASES.  Now, this may have something
to do with the setup of reading sockets for the output.  I do not know.
I do know that it means that if I do not try to stop a window in the
instant before output beings, I am stuck watching the output until
a pause occurs.  And of course, fgrep , etc. never pause.

Other than never making mistakes, or powering off my terminal, what
kinds of changes could be made to a program like screen to become
sensitive to user input requests during output?  Remember there are two
types of user input!  There are the input strokes to the current application
and there are input strokes intended for screen.  The ones intended
for screen are the ones I would like to take place at the instant, or
soon there after, that they occur.
--
Larry W. Virden                 UUCP: osu-cis!chemabs!lwv27
Same Mbox: BITNET: lwv27@cas    INET: lwv27%cas.BITNET@CUNYVM.CUNY.Edu
Personal: 674 Falls Place,   Reynoldsburg,OH 43068-1614
America Online: lvirden