* Ebola
@ 2001-01-07 22:48 Gunnar Evermann
2001-01-07 23:11 ` Ebola Karl Kleinpaste
0 siblings, 1 reply; 2+ messages in thread
From: Gunnar Evermann @ 2001-01-07 22:48 UTC (permalink / raw)
In Oort Gnus v0.01 cvs of today on XEmacs21.1.13 I get loads of
messages like the following.
Comparison between integer and character is constant nil (?0 and 1)
[parse-time-tokenize, parse-time-string, byte-code, date-to-time,
article-make-date-line, article-date-ut, article-date-lapsed,
<compiled-function of unknown origin>, walk-windows, byte-code,
article-update-date-lapsed, (lambda nil
(article-update-date-lapsed)), byte-code,
itimer-run-expired-timers, itimer-timer-driver]
This is with gnus-start-date-timer.
Gunnar
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Ebola
2001-01-07 22:48 Ebola Gunnar Evermann
@ 2001-01-07 23:11 ` Karl Kleinpaste
0 siblings, 0 replies; 2+ messages in thread
From: Karl Kleinpaste @ 2001-01-07 23:11 UTC (permalink / raw)
Gunnar Evermann <ge204@eng.cam.ac.uk> writes:
> In Oort Gnus v0.01 cvs of today on XEmacs21.1.13 I get loads of
> messages like the following.
> Comparison between integer and character is constant nil (?0 and 1)
Anything to do with Date hackery (timers, or X-Sent substitution)
induces this. The fix is to recompile XEmacs without debugging, or
alternatively to edit xemacs/src/data.c to comment out the relevant
debug warning message. It's pointless, and can be triggered by many
other things besides Gnus' date calculations.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-01-07 23:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-07 22:48 Ebola Gunnar Evermann
2001-01-07 23:11 ` Ebola Karl Kleinpaste
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).