Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!pur-ee!ea.ecn.purdue.edu!wieland
From: wieland@ea.ecn.purdue.edu (Jeffrey J Wieland)
Newsgroups: comp.mail.elm
Subject: Re: Behavior of ' ' considered inconsistant
Message-ID: <11743@ea.ecn.purdue.edu>
Date: 16 May 89 13:24:37 GMT
References: <377@ladcgw.UUCP> <17839@cos.com> <9336@b-tech.ann-arbor.mi.us> <32@wave4.webo.dg.com>
Reply-To: wieland@ea.ecn.purdue.edu.UUCP (Jeffrey J Wieland)
Organization: Purdue University Engineering Computer Network
Lines: 28

In article <32@wave4.webo.dg.com> tom@wave4.dg.com (Tom Jordahl) writes:
>In article <9336@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
>>>I would rather see enhancements to the pager that noone has objected to,
>>>such as being able to scroll backwards within a message, like less.
>>
>>I would definitely like to see someone add this.  Even a simple 1 page
>>scroll back would be useful.
>
>I simply use less as the default pager.  Do many people do this?  Is more
>used for this default?  Why would you use the built-in pager if more powerfull
>pagers are "standard" ( I am referring to more here) on your system?
>
>just curious

We use the builtin pager because of the large startup overhead for
our machines -- most of them are quite memory starved, and it can
take quite a while for "pg" or "more" to start up.  While elm takes
longer to start up than, say, mailx, (due to its larger size) once
it gets going it is much faster to use.

A comment on an earlier message -- I would also like to see the
functionality of "readmsg" moved into elm.  It can take 10 minutes
or more to save 80 messages to a file, because readmsg must be
invoked by elm for each one.  Mailx does this much faster.  Readmsg
is still useful as a standalone program.

			    Jeff Wieland
			wieland@ecn.purdue.edu