Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!rochester!bullwinkle!gvax!jqj
From: jqj@gvax.cs.cornell.edu (J Q Johnson)
Newsgroups: net.unix-wizards
Subject: Re: to job control or not to job control (was UNIX Futures)
Message-ID: <304@gvax.cs.cornell.edu>
Date: Sun, 13-Apr-86 06:06:49 EST
Article-I.D.: gvax.304
Posted: Sun Apr 13 06:06:49 1986
Date-Received: Sun, 20-Apr-86 05:14:28 EST
References: <67@cstvax.UUCP> <2864@amdahl.UUCP> <137@myab.UUCP> <6571@utzoo.UUCP> <158@cad.UUCP> <279@maynard.UUCP>
Reply-To: jqj@cornell.UUCP (J Q Johnson)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 14

In article <279@maynard.UUCP> campbell@maynard.UUCP (Larry Campbell) writes:
>> ...if the program isn't prepared to redisplay output, no matter whether
>> or not you have job control it's going to scroll off the screen anyway.
>It doesn't scroll off the screen if you go open another window to do
>subsequent stuff.  

Presumably, any reasonable window system (e.g. the one we run on our Xerox
Dandelions) will have a mode of operation in which text is logged locally
as it scrolls out of the window.  Such text can then be reviewed in the
same or a different window, much as one can fumble through the paper that
spews out of a hardcopy terminal.

Note that this implicit definition of "reasonable" excludes most of the
window systems that have been mentioned recently on this list.