Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: Paging should come before multiplexing
Message-ID: <11248@smoke.BRL.MIL>
Date: 7 Oct 89 02:24:42 GMT
References: <295@nisca.ircc.ohio-state.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <295@nisca.ircc.ohio-state.edu> bernstei@hpuxa.ircc.ohio-state.edu (Dan Bernstein) writes:
-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.

??? Perhaps you should explain what your model of "multiplexing" is.
My terminal runs multiplexed much of the time, but each output is
demuxed to a different window and can be controlled separately.
I shudder to think of trying to visually demux intermixed output.