Re: [PATCH] Use shell-command-on-region in pgg-gpg.el

[Niklas Morberg <niklas.morberg@axis.com>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Niklas Morberg <niklas.morberg@axis.com> writes:
>
>>>> In pgg-gpg.el, the function pgg-gpg-process-region uses
>>>> call-process-region. My guess is that call-process-region
>>>> does not use my proxy settings (defined in .emacs with
>>>> setenv).
>
> I'm kinda surprised that that would make any difference.  If the
> command uses environment variables, it should heed them in any case,
> shouldn't it?

There certainly is a difference, at least on my system
(cygwin). I don't know why. The following small test case,
using search.keyserver.net which is only available through
my proxy, shows it:

Evaling the following in the *scratch* buffer: 

  (shell-command-on-region (point) (point) "gpg --recv-keys 0x80808080" t)

Returns immediately with the following result:

gpg: requesting key 80808080 from search.keyserver.net
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

Evaling the following in the *scratch* buffer: 

  (call-process-region (point) (point) "gpg" nil t nil "--recv-keys" "0x80808080")

Hangs for a while and then returns:

gpg: requesting key 80808080 from search.keyserver.net
gpg: can't get key from keyserver: Connection timed out
gpg: Total number processed: 0

If I do the same but use a local keyserver (by modifying
~/.gnupg/gpg.conf) both functions return immediately with
the identical output:

gpg: requesting key 80808080 from keys.axis.se
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

Niklas