Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!nisca.ircc.ohio-state.edu!hpuxa.ircc.ohio-state.edu!bernstei
From: bernstei@hpuxa.ircc.ohio-state.edu (Dan Bernstein)
Newsgroups: comp.unix.wizards
Subject: Paging should come before multiplexing
Message-ID: <295@nisca.ircc.ohio-state.edu>
Date: 8 Oct 89 04:22:08 GMT
Sender: news@nisca.ircc.ohio-state.edu
Distribution: usa
Lines: 14

If paging comes after multiplexing, then it can't be used to cut off a
long output, because it can't distinguish that long output from short
outputs multiplexed into the middle.

I don't want a simplistic pager whose only functions are to slow down
the output so that I can read it, and to make me type ^Q after every
page. I want a pager that can cut off the remaining pages---so I will
not put my pager in the terminal.

This argument does not apply to ``simplistic'' pagers, and it would not
apply if the distinctions between processes could be preserved through
multiplexing.

---Dan Bernstein, brnstnd@acf10.nyu.edu, bernstei@hpuxa.ircc.ohio-state.edu