Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!udel!mmdf
From: waltje@minixug.hobby.nl (Fred van Kempen)
Newsgroups: comp.os.minix
Subject: (none)
Message-ID: <25616@nigel.udel.EDU>
Date: 25 Jul 90 17:34:31 GMT
Sender: mmdf@ee.udel.EDU
Lines: 31

Subject: Re: p.c for Minix (more(1) replacement)
Newsgroups: comp.os.minix
References: <1990Jul23.011015.15237@jarvis.csri.toronto.edu>

From article <1990Jul23.011015.15237@jarvis.csri.toronto.edu>, by wayne@csri.toronto.edu (Wayne Hayes):
> 
> Here is p(1) for Minix.  It is a simple replacement for more(1), because
> I'm sick of the long delay it takes more to start up.  Has anyone else
> wondered why such a simple program takes so loooong to start up?  Sheesh.
You probably allocated too little stack space to it; the program needs a
fair amount of (malloc'ed !) buffer space.  It is probably the same problem
as with the clr(1) program a while ago.
I have no problems whatsoever with the current more(1).  I also still have
the old more(1) online (as "omore").

>     For p(1), you just press return for each new screen or press q{return}
> to quit.  It accepts piped input, and accepts an optional single option
> to set the screen size in lines (default 23, which allows 1 or 2 lines
> overlap between screens).  It'll also take an arbitrary number of files on
> the command line.  It should also compile on any UNIX box.  Hey, now that
> I think of it, it'll probably compile *anywhere*, it's not that specialized...
Hmm, sounds like the old more(1) to me.  However, that one used termcap(3)
for all screen stuff....

+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| MINIX User Group Holland	  UUCP: waltje@minixug.hobby.nl |
| c/o Fred van Kempen,		    or: hp4nl!minixug!waltje    |
| Hoefbladhof  27		                  		|
| 2215 DV  VOORHOUT	"Love Is- what you want it to be.	|
| The Netherlands			Allannah Myles"		|
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+