From: Steve Youngs <steve@youngs.au.com>
Subject: Re: timers and itimers
Date: Thu, 27 Jan 2005 12:10:11 +1000 [thread overview]
Message-ID: <microsoft-free.87r7k7bp18.fsf@youngs.au.com> (raw)
In-Reply-To: <b9yfz0nr83i.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 27 Jan 2005 10:09:21 +0900")
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
* Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> * Romain Francoise <romain@orebokech.com> writes:
>>> Please keep in mind that the supported versions for Gnus v5.10 are
>>> XEmacs 21.1 and up; for No Gnus the supported versions are 21.4
>>> and up.
>>>>>> In <microsoft-free.87vf9jbzoa.fsf@youngs.au.com> Steve Youngs wrote:
>> Sure will. This stuff comes from the packages so there won't be a
>> problem.
> Unfortunately, the new xemacs-base package doesn't help all
> the versions of XEmacsen.
It helps enough, because...
>>>>>> In <b9y651kq34y.fsf@jpl.org> Katsumi Yamaoka wrote:
>> Although there will be many users who seldom upgrade XEmacs and
>> packages, I think it is worth deleting run-at-time.el and
>> recommending people the use of the new package.
> It was necessary to add ``and new XEmacs'' to the last paragraph,
> sorry.
> Because of a bug in itimer.el which is embedded in the XEmacs
> core, even the run-at-time function in the new xemacs-base
> package won't work correctly with old XEmacsen. I posted a
> patch in December 2003[1], Vin Shelton applied it to XEmacs 21.4
> in January 2004[2], and Jerry James applied it to XEmacs 21.5 in
> September 2004[3]. Therefore, XEmacs 21.4.15 and 21.5.18 will
> run timer functions correctly. I didn't thoroughly check them
> with old XEmacsen, though.
> Anyway, can't we fire old XEmacsen even in Gnus v5.10?
...yes. From XEmacs.org's point of view, packages only have to
support from 21.4 onwards.
--
|---<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 --]
next prev parent reply other threads:[~2005-01-27 2:10 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 [this message]
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
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.87r7k7bp18.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).