--Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
Alas! David T-G spake thus: > What I need to know now is how mutt calls gpg so that it gets a key; It's obvious you know a lot more about GPG than I do (I didn't even know there was a new version until reading this), but try writing a bash script that contains this: #!/bin/bash echo "$*" > ~/args cat > ~/stdin Then replace your gpg binary with that command. Then run mutt. Now check your home dir, and you'll see the two files, and you'll know how mutt calls gpg ;) --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- Beauty may be skin deep, but ugly goes clear to the bone. -- Redd Foxx --Qxx1br4bt0+wmkIi 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 iD8DBQE84x+3PTh2iSBKeccRAmJAAJ4tOGtSqR4nSVd/wjMcqlraMf7VJACaAm/8 r9vcPlygtOjE4VoHxuisl4c= =KIgN -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--
