From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [PATCH] Use shell-command-on-region in pgg-gpg.el
Date: Tue, 13 May 2003 20:09:35 +0200 [thread overview]
Message-ID: <m3fzniwwf4.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <uy91go3o2.fsf_-_@axis.com>
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?
> I haven't been able to test the original implementation
> (since call-process-region does not use my proxy settings)
> and don't know if the output from the command is supposed to
> pop up in a new frame. Now it does.
It's not supposed to do that, which is why one doesn't use
`shell-command*' in programs.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-05-13 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 14:07 Getting gpg (or is it pgg?) to play nice with proxy Niklas Morberg
2003-04-17 8:57 ` Niklas Morberg
2003-04-25 9:53 ` Niklas Morberg
2003-05-09 9:44 ` [PATCH] Use shell-command-on-region in pgg-gpg.el (was: Getting gpg (or is it pgg?) to play nice with proxy) Niklas Morberg
2003-05-13 18:09 ` Lars Magne Ingebrigtsen [this message]
2003-05-14 7:15 ` [PATCH] Use shell-command-on-region in pgg-gpg.el Niklas Morberg
2003-05-14 8:31 ` Simon Josefsson
2003-05-14 9:51 ` Niklas Morberg
2003-05-14 9:59 ` Simon Josefsson
2003-05-16 16:41 ` Dave Love
2003-05-10 8:03 ` Getting gpg (or is it pgg?) to play nice with proxy Simon Josefsson
2003-05-12 9:16 ` Niklas Morberg
2003-05-12 12:05 ` Simon Josefsson
2003-05-13 7:43 ` Niklas Morberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fzniwwf4.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).