From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: pgg.el and run-at-time
Date: Tue, 09 Dec 2003 17:45:34 +0100 [thread overview]
Message-ID: <iluwu96vt1t.fsf@latte.josefsson.org> (raw)
In-Reply-To: <b9y8ylm6xkj.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 09 Dec 2003 20:27:08 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Hi,
>
> I noticed the run-at-time function of the XEmacs version doesn't
> work correctly, which runs a timer function almost immediately
> at the first time, ignoring the specified time, and reported it
> to the XEmacs-beta list today.
>
> Also I found pgg.el uses run-at-time directly. Although I'm not
> using pgg, I'm afraid that the cached passphrase may immediately
> be expired. Is it better to replace it with nnheader-run-at-time?
I think PGG should not depend on Gnus files, but we could create a
pgg-run-at-time and use that.
Does XEmacs support run-at-time at all, or is it obsolete FSF
compatibility functionality? I could not find neither documented in
the XEmacs Lispref manual.
next prev parent reply other threads:[~2003-12-09 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 11:27 Katsumi Yamaoka
2003-12-09 16:45 ` Simon Josefsson [this message]
2003-12-10 0:36 ` Katsumi Yamaoka
2003-12-10 6:35 ` Katsumi Yamaoka
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=iluwu96vt1t.fsf@latte.josefsson.org \
--to=jas@extundo.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).