From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: gpg.el still not working
Date: Tue, 24 Sep 2002 10:58:00 -0400 [thread overview]
Message-ID: <87u1kfxwnb.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <ilu4rcfaaya.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> `call-process-region' seem to return nil, but according to the
> documentation for that function it should never do this unless
> buffer was NIL, which wasn't the case here. Maybe you can strip
> down the code and make a bug report (or discover why this happens)?
I believe I responded about this the last time the question was asked.
See: <87u1lu52se.fsf@mail.paradoxical.net>
Jack, you asked this about a month ago, and I'm pretty sure the answer
is the same. Have you tried updating your XEmacs cvs?
--
Josh Huber
next prev parent reply other threads:[~2002-09-24 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 2:18 Jack Twilley
2002-09-23 10:31 ` Simon Josefsson
2002-09-23 12:45 ` Kai Großjohann
2002-09-23 21:52 ` Jack Twilley
2002-09-24 11:22 ` Simon Josefsson
2002-09-24 14:58 ` Josh Huber [this message]
2002-09-24 17:06 ` Jack Twilley
2002-09-24 17:27 ` Josh Huber
2002-09-24 18:54 ` Jack Twilley
2002-09-24 20:17 ` Josh Huber
2002-09-25 0:55 ` Jack Twilley
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=87u1kfxwnb.fsf@mail.paradoxical.net \
--to=huber@alum.wpi.edu \
--cc=huber+dated+1033310821.45e3d4@alum.wpi.edu \
/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).