Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!crowl
From: crowl@cs.rochester.edu (Lawrence Crowl)
Newsgroups: comp.arch
Subject: Re: paging in the terminal driver
Message-ID: <3619@sol.ARPA>
Date: Tue, 27-Oct-87 09:19:41 EST
Article-I.D.: sol.3619
Posted: Tue Oct 27 09:19:41 1987
Date-Received: Thu, 29-Oct-87 21:53:50 EST
References: <573@elxsi.UUCP> <682@its63b.ed.ac.uk> <796@quacky.UUCP> <421@nuchat.UUCP>
Reply-To: crowl@cs.rochester.edu (Lawrence Crowl)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 16
Keywords: output pagination

In article <421@nuchat.UUCP> steve@nuchat.UUCP (Steve Nuchia) writes:
[Is screen paging embedded in the terminal driver good?]
>There is no describing the feeling of coming back from a meeting or extended
>coffee expedition to find that the compile you fired off half an hour ago only
>got through the first screenful of compiler version number announcements.
>GRRRR!

This is easily fixed by sending the program output to a file and then having
the terminal driver display the file.  This approach provides both paging and 
long untended output.  The shell could provide this transparently.  The
disadvantages are that one is spending more time doing file i/o, and that
nearly full file systems will fill up.  These are costs worth paying.
-- 
  Lawrence Crowl		716-275-9499	University of Rochester
		      crowl@cs.rochester.edu	Computer Science Department
...!{allegra,decvax,rutgers}!rochester!crowl	Rochester, New York,  14627