--zS7rBR6csb6tI2e1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Volker Moell ([EMAIL PROTECTED]) [020125 14:45]:
> > % mail). It would be so much easier for everyone if check-traditional-=
pgp
> > % would become a variable ("set always-check-traditional-pgp=3Dyes"), so
> > % that every mail will be checked automatically on demand (instead of
> > % handling 50% of all mail accesses via macros and doing some terrible
> > % workarounds for the other 50%).
> > Hmmm...
>=20
> With this I mean, you can
> - press <enter> in the index
> - press <down>, <up>, <pgup>, <pgdown> in the pager
> - press <space> at the end of a message
> - delete (in various ways) a mail
> - jump to a mail
> - ...
> to view a mail. Do you really want do set a macro for each of these (and
> surely more!) keybindings? Not really, at least not me. So a message-hook
> seems to be the only senseful place to implement a "check-traditional on
> demand". With macros it's only a nice workaround. IMHO.
Sorry, I'm jumping into the thread late, so I may end up looking like an
ignorant ass, but I'll take my chances anyway and offer you another
workaround. (I think) one issue of mutt detecting the old-style messages
is looking through the body of each message to see if it fits a certain
pattern, which is seen (understandably so) as something expensive that
mutt shouldn't be doing anyway. The workaround I propose, for you and
anyone else in your boat, is to set your pager to something (a small
perl script) that can recognize old-style pgp messages and pipe those to
gpg for processing, then display the message via a real pager (i.e. less
or some such).
That's *kinda* like a user-space message-hook, except it happens for
each message instead of only ones that match a certain pattern. You
might be able to fenagle it to working with a message-hook by setting
pager selectively or some other dirty hacks, but I'd say to try to get
it working everywhere first before optimizing it so.
I'll help you with the script if you need it; I think it should be as
simple as taking the patterns from the ubiquitous procmail example and
putting them in a 5-line perl script.
good times,
Vineet
--=20
Currently seeking opportunities in the SF Bay Area
Please see http://www.doorstop.net/resume/
--=20
Satan laughs when we kill each other. Peace is the only way.
--zS7rBR6csb6tI2e1
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjxYTbsACgkQ7z3S33fUb9GyEwCguccN8IXyfeVi3qFQ/xIZjmMk
fIUAn1v8DDUUr52ifSQBTPz3P6i134NC
=LPHw
-----END PGP SIGNATURE-----
--zS7rBR6csb6tI2e1--
