From: Lee Willis <lee@gbdirect.co.uk>
Subject: Re: mailcrypt
Date: 23 Apr 1999 17:27:27 +0100 [thread overview]
Message-ID: <lz90bj480g.fsf@landlord.gbdirect.co.uk> (raw)
In-Reply-To: =?iso-8859-1?q?Fran=E7ois?= Pinard's message of "Fri, 23 Apr 1999 12:06:35 -0400"
François Pinard <pinard@iro.umontreal.ca> writes:
> > 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 think he was implying that if you're running byte-compiled code it
must be byte-compiled for the correct version of Emacs that you are
using, ie you can't run a PGP compiled for emacs 19.34 with say emacs
20.3, or something to that effect rather than it being a byte-compiled
versus source issue.
Lee.
--
I was doing object-oriented assembly at 1 year old ...
For some reason my mom insists on calling it "Playing with blocks"
next prev parent reply other threads:[~1999-04-23 16:27 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 ` mailcrypt William M. Perry
1999-04-23 16:27 ` Lee Willis [this message]
-- 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=lz90bj480g.fsf@landlord.gbdirect.co.uk \
--to=lee@gbdirect.co.uk \
/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).