Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ptsfa!ihnp4!cuae2!cuuxb!ltuxa!ttrdc!levy
From: levy@ttrdc.UUCP (Daniel R. Levy)
Newsgroups: comp.unix.wizards
Subject: Re: Pager in the shell
Message-ID: <1935@ttrdc.UUCP>
Date: Sun, 18-Oct-87 15:30:33 EDT
Article-I.D.: ttrdc.1935
Posted: Sun Oct 18 15:30:33 1987
Date-Received: Wed, 21-Oct-87 22:41:36 EDT
References: <9779@brl-adm.ARPA>
Organization: AT&T, Skokie, IL
Lines: 21

In article <9779@brl-adm.ARPA>, mills%cc.uofm.cdn%ubc.csnet@RELAY.CS.NET (Gary Mills) writes:
> Has anyone succeeded in putting a pager into the shell?  I am getting
> a bit tired of appending ` | pg' to any command line that I suspect
> will generate more than a screen of output...
> I'm not asking for too much,
> am I? :-)  This is System V and we have source.

Sorry for the post, but the return address looked forbidding.  A "pager in the
shell" would require piping the standard output of commands into some kind
of paginator process just like you do manually now with "| pg".  I daresay this
would cause problems with programs that want to do raw output, like "vi" and
other screen-oriented stuff, because they are expecting to output directly to
your terminal, not into a pager.  The only other remotely reasonable way you
could get between a program's output and your terminal to paginate it is to
kludge the terminal driver in the kernel so it would paginate in cooked mode
but not in raw mode.  (Has anyone been crazy enough to try this?)
-- 
|------------Dan Levy------------|  Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
|         an Engihacker @        |		vax135}!ttrdc!ttrda!levy
| AT&T Computer Systems Division |  Disclaimer?  Huh?  What disclaimer???
|--------Skokie, Illinois--------|