Gnus development mailing list
 help / color / mirror / Atom feed
From: SL Baur <steve@xemacs.org>
Subject: Re: mailcrypt error
Date: 10 Sep 1998 14:21:41 -0700	[thread overview]
Message-ID: <m2ww7b1x5m.fsf@altair.xemacs.org> (raw)
In-Reply-To: Karl Kleinpaste's message of "10 Sep 1998 08:09:08 +-400"

Karl Kleinpaste <karl@jprc.com> writes in ding@gnus.org:

> Phil Humpherys <phumpherys@utah-inter.net> writes in ding@gnus.org:
>>> I had text in a mail buffer, and did M-x mc-encrypt...
>>> Cannot open load file: timer

Phil, could you please (setq debug-on-error t) and get a lisp stack
backtrace?

> SL Baur <steve@xemacs.org> writes:
>> Uh oh.  This isn't Gnus-related.  Get the mailcrypt folks to use
>> itimers instead of timers in XEmacs.

> mailcrypt 3.5b5 comes with its own timer package, as FSF-timer.el,
> which the install procedure puts into place as timer.el.  So if the
> install is done normally, the timer.el problem is already covered.

O.K.  I've taken a look at the code.  I believe the problem is that
the FSF-timer.el in mailcrypt shouldn't be installed.  It is expecting 
to be able to run a program called `timer' in the background.

The new mailcrypt appears to be coded as correctly as the old mailcrypt
wrt timers.  The code first looks for itimer, and if it doesn't find
it, falls back to timer.  I know that code works in both emacsen and
it doesn't appear to have changed.


      reply	other threads:[~1998-09-10 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-10  7:21 Phil Humpherys
1998-09-10  8:35 ` SL Baur
1998-09-10  4:09   ` Karl Kleinpaste
1998-09-10 21:21     ` SL Baur [this message]

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=m2ww7b1x5m.fsf@altair.xemacs.org \
    --to=steve@xemacs.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).