Hi,
Thanks for tracking my patch.
>>>> In <m3vfmvfrjx.fsf(a)zion.rcn.com>
>>>> Vin Shelton <acs(a)xemacs.org> wrote:
If so, maybe I could sneak it into 21.4.15.
>>>> In
<bv96ru$prudh$1(a)ID-36780.news.uni-berlin.de>
>>>> Hans-Joachim Daniels <hajo.daniels(a)gmx.de> wrote:
(1) (error/warning) Error in pre-gc-hook: (wrong-type-argument listp
t)
(2) (error/warning) Error in `post-command-hook' (setting hook to
nil):
(error itimer timeout value not positive: 0.0)
Although I don't know how jde uses timer functions, it doesn't
seem to happen by the itimer.el bug which I raised. It is more
likely that such an error occurs when starting a timer with the
zero argument or restarting a timer which has been reached to
the specified time. I couldn't find the former case in the jde
package but I found a code which looks like a bug in jde-parse.el.
It may create zombie timers having the zero value:
--- jde-parse.el~ 2003-01-26 22:08:11 +0000
+++ jde-parse.el 2004-01-29 04:41:17 +0000
@@ -135,7 +135,7 @@
(if (timerp jde-auto-parse-buffer-timer)
(let ((rem (jde-auto-parse-delay)))
(cond
- ((< rem 0)
+ ((<= rem 0)
;; Timer has expired, re-schedule a new auto-parse.
(cancel-timer jde-auto-parse-buffer-timer)
(setq jde-auto-parse-buffer-timer nil))
I'm not sure whether this is related to Hans-Joachim's problem,
though.
Regards,
--
Katsumi Yamaoka <yamaoka(a)jpl.org>