Re: exmh and gnupg (and a 3-year-old bug)

On Mon, 14 Jul 2003 17:31:38 CDT, Hal DeVore <[email protected]>  said:

> Don't worry about being new to Tcl/Tk.  
> 
> Seriously.

Really.  If *I* can mostly get Tcl's quoting rules correct, anybody can.

Though looking at the fact that the value of '*pgpComment:' in my
.exmh/exmh-defaults is borked indicates that I don't understand them as
well as I thought. :)

*pgpComment: Exmh version 2.5 07/13/2001

Damn. I see the bug - it took 13 months for it to bite me. ;)

When I wrote the code in 06/2000, it did the neat trick of inserting a PGP
Comment: header with either a user-specified string, or the eval-at-runtime
value of 'Exmh [set exmh(version)]'  so it would tell us what Exmh release
borked things up if there was an issue (remember that the X-Mailer: header is
subject to mangling/lossage).  When Brent tagged and released 2.5 (is this
software or wildlife??), something decided to mis-eval/quote and decide that it
was user-modified and saved it to .exmh/exmh-defaults.  Of course, after that,
it was a user-supplied string and not subject to further updating....

The *robust* fix would be to just use the user-supplied string if any, or the Exmh
version if none.  I'm open to suggestions as to whether I should check the
user string for the pattern 'Exmh version \d+\.\d+ \d+/\d+/\d+' and toss,
to clean out everybody (like me) that has a stale version value in there. 

/Valdis

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE/Ez/fcC3lWbTT17ARArB6AJ9H8FrDDiZ63gbT/FIHtvsiuijl9QCgjL7/
sOeQw/IB/22yfJ3qris/xdA=
=l8an
-----END PGP SIGNATURE-----