Re: pgp_autosign=ask-no
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, October 2 at 11:15 PM, quoth Joseph:
> Thanks Kyle again, yes it works as you explained.
:)
> One more thing, when I was going through gpg.rc enclosed with
> distribution it listed this entry, but it was commented out:
> # fetch keys
> # set pgp_getkeys_command="pkspxycwrap %r"
>
> but when I enable it I got:
>
> Fetching PGP key...sh: pkspxycwrap: command not found
> set pgp_getkeys_command="pkspxycwrap %r"
Well, like all the pgp_*_command settings, it's a command-line shell
command that you want mutt to execute in order to achieve a specific
task. In this case, according to the documentation:
This command is invoked whenever mutt will need public key
information.
Mine is set to this:
set pgp_getkeys_command="gpg --recv-keys %r"
But then again, I'm not 100% certain when mutt uses it (I'd have to
dig through the source to find out for sure). I use gpg very
frequently, and this has never been an issue for me. I *think* it may
be a way to make mutt fetch public keys manually... but since I
automate it (by telling gpg to automatically fetch keys), I just don't
futz with it. :)
~Kyle
- --
As an adolescent I aspired to lasting fame, I craved factual
certainty, and I thirsted for a meaningful vision of human life. So I
became a scientist. This is like becoming an archbishop so you can
meet girls.
-- M. Cartmill
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFHAycuBkIOoMqOI14RApBAAJ0Ts/0kwiTxYquIDslL5nUB71JjBQCfRRc0
fdeRg9fxtinEVZEF23R1s+o=
=w4FH
-----END PGP SIGNATURE-----