From: wmperry@aventail.com (William M. Perry)
Cc: ratinox@peorth.gweep.net, ding@gnus.org
Subject: Re: mailcrypt
Date: 23 Apr 1999 11:19:39 -0500 [thread overview]
Message-ID: <86676nl36s.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: François Pinard's message of "Fri, 23 Apr 1999 12:06:35 -0400"
François Pinard <pinard@iro.umontreal.ca> writes:
> Hi, people. I was re-reading old mail.
>
> > PH> I have PGP 5.0, and had mailcrypt working fine under emacs, but
> > PH> when I went to xemacs (20.4), I get an error message when I fire
> > PH> up emacs that states that it can't set version 5.0.
>
> > mailcrypt must be byte-compiled for the Emacs and Gnus you are using,
> > otherwise it will not work.
>
> How could it make such a difference? I thought that running byte-compiled or
> not should not make a difference, or else, I would see a bug. Don't you?
I believe the problem with mailcrypt is that it uses some 'internal'
functions to Gnus that are macros, so the do not play well when switching
from version to version (of Gnus).
I don't know why you have to recompile for Emacs->XEmacs other than the
obvious mule stuff.
-Bill P.
next prev parent reply other threads:[~1999-04-23 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-07 6:02 mailcrypt Phil Humpherys
1998-09-07 6:39 ` mailcrypt Stefan Waldherr
[not found] ` <x7btorn22v.fsf@peorth.gweep.net>
1998-09-08 0:33 ` mailcrypt Phil Humpherys
1999-04-23 16:06 ` mailcrypt François Pinard
1999-04-23 16:14 ` mailcrypt Alexandre Oliva
1999-04-23 16:43 ` mailcrypt François Pinard
1999-04-23 16:19 ` William M. Perry [this message]
1999-04-23 16:27 ` mailcrypt Lee Willis
-- strict thread matches above, loose matches on Subject: below --
1998-08-24 3:54 mailcrypt Phil Humpherys
1998-08-25 5:54 ` mailcrypt Lars Magne Ingebrigtsen
1998-08-23 3:56 mailcrypt Phil Humpherys
1998-08-23 12:29 ` mailcrypt Lars Magne Ingebrigtsen
1998-08-23 18:30 ` mailcrypt Dave Love
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=86676nl36s.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.com \
--cc=ding@gnus.org \
--cc=ratinox@peorth.gweep.net \
/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).