1993-11-11 - Elm & PGP

Header Data

From: lear35!mdbomber@nebula.acs.uci.edu (Matt Bartley)
To: cypherpunks@toad.com
Message Hash: ec24823fba1f4705cbd7ddc649ac00f14b3fdd064aab8dfdd06db11d97fb3721
Message ID: <9311110647.AA19765@lear35.vlpa.ca.us>
Reply To: N/A
UTC Datetime: 1993-11-11 11:13:29 UTC
Raw Date: Thu, 11 Nov 93 03:13:29 PST

Raw message

From: lear35!mdbomber@nebula.acs.uci.edu (Matt Bartley)
Date: Thu, 11 Nov 93 03:13:29 PST
To: cypherpunks@toad.com
Subject: Elm & PGP
Message-ID: <9311110647.AA19765@lear35.vlpa.ca.us>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----


I'm having some trouble using the morepgp filter program that's in the
contrib/elm_nn directory of the PGP distribution.  It works nicely in
most respects.  However, I haven't been able to choose a good pager
program for morepgp to send its output to.

If I tell morepgp to use the 'more' program, it will page through the
mail message until it gets to the end.  When that happens, elm
suddenly retakes control and clears the screen.  The last screenful of
the message is therefore on the screen only an instant.  This is
unacceptable.

A lesser problem is when the mail message has a PGP signature.  As pgp
works on it, it will say something to the effect of
	good signature from <user> at <timestamp>
However, it immediately passes control to more, which doesn't pause the
screen until the "good signature" message has already scrolled off the
screen.  At least in an xterm window I can scroll back.

Speaking of less, that's the default pager for morepgp, but it has
problems also.  It has the same problem as more where the pgp
signature information scrolls off the screen before it can be read.
However, since less clears the screen between each screenful, there is
no way to scroll back using the scroll bars of an xterm window.  Thus
I only get a few miliseconds to read whether whose signature was on
that mail message I just read...  I haven't found any command line options
for less that disable the screen clears.

Does anyone have any solutions to this problem?


-----BEGIN PGP SIGNATURE-----
Version: 2.3a

iQBVAgUBLOHgEjSSmvXojb+5AQH1/wH6A7j1dZalFHIIZXLxl0OW4K/CgA/hAZ0G
SV2RAe5k5fDIY52JCJoFgtwL7fam0YQ+eifveIoCkkLV2EOP4ZXtUg==
=4ctR
-----END PGP SIGNATURE-----




Thread