From: Steve Youngs <steve@youngs.au.com>
Subject: Re: timers and itimers
Date: Thu, 27 Jan 2005 08:19:19 +1000 [thread overview]
Message-ID: <microsoft-free.87zmyvbzq0.fsf@youngs.au.com> (raw)
In-Reply-To: <iluzmywjy27.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 26 Jan 2005 11:15:44 +0100")
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
* Simon Josefsson <jas@extundo.com> writes:
> Steve Youngs <steve@youngs.au.com> writes:
>> I've just committed a patch that cleans up all of the timer code for
>> XEmacs, including removing run-at-time.el.
> ...
>> This clean up is definitely needed in the 5.10 branch so I'll commit a
>> similar patch there a little later tonight.
> Do XEmacs 21.1 have the working timer function, that your patch uses?
> Gnus 5.10 is supposed to work on it.
Of course, timer-funcs.el is in the xemacs-base package so it is
available to all versions of XEmacs from 21.0 onwards.
>> For the GNU people who are interested, timer-funcs.el provides the
>> following functions:
> Would it be useful to name timer-funcs.el timer.el, so the same
> `require' line work for both GNU and XEmacs?
I would think not. There is nothing common to both libraries, and
nothing of what is left in the fsf-compat package timer.el is used in
Gnus.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Te audire no possum. |
| Musa sapientum fixa est in aure. |
|----------------------------------<steve@youngs.au.com>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
prev parent reply other threads:[~2005-01-26 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 9:11 Steve Youngs
2005-01-26 9:29 ` Romain Francoise
2005-01-26 22:20 ` Steve Youngs
2005-01-27 1:09 ` Katsumi Yamaoka
2005-01-27 2:10 ` Steve Youngs
2005-01-27 2:37 ` Katsumi Yamaoka
2005-01-27 4:43 ` Steve Youngs
2005-01-27 5:43 ` Katsumi Yamaoka
2005-01-26 10:15 ` Simon Josefsson
2005-01-26 22:19 ` Steve Youngs [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=microsoft-free.87zmyvbzq0.fsf@youngs.au.com \
--to=steve@youngs.au.com \
/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).