From: Charles Sebold <csebold@ezl.com>
Cc: Charles Sebold <csebold@ezl.com>, ding@gnus.org
Subject: Re: Problems with mailcrypt/gpg
Date: 14 Dec 2000 08:34:42 -0600 [thread overview]
Message-ID: <m3n1dzdqbh.fsf@sebold.lcms.org> (raw)
In-Reply-To: <vzlmtjyt7y.fsf@lamia.LF.net>
On 17 Kislev 5761, Norbert Koch wrote:
> No, unfortunately, there's still something missing. I'm running a
> current CVS and I have all these settings activated... still the same
> behaviour :-(
Sorry for the un-help, then. I'm running GNU Emacs 20 and 21-pre, so
perhaps it's an XEmacs thing now. But I'm pretty sure that somebody
concurred that it worked on their XEmacs setup when I had my problem.
Hm.
--
Charles Sebold
--
17th of Kislev, 5761
--
Tech Support excuse #374:
It's the InterNIC's fault.
next prev parent reply other threads:[~2000-12-14 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 13:55 Norbert Koch
2000-12-14 14:15 ` Charles Sebold
2000-12-14 14:26 ` Norbert Koch
2000-12-14 14:34 ` Charles Sebold [this message]
2000-12-14 15:57 ` ShengHuo ZHU
2000-12-14 16:08 ` Norbert Koch
2000-12-14 16:07 ` Jeff Senn
2000-12-15 5:29 ` ShengHuo ZHU
2000-12-15 15:38 ` Jeff Senn
2000-12-20 3:05 ` ShengHuo ZHU
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=m3n1dzdqbh.fsf@sebold.lcms.org \
--to=csebold@ezl.com \
--cc=ding@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).