Strange message dumped to shell when article selected

Strange message dumped to shell when article selected

[Tony Lam]

Gnus 5.8.8
XEmacs 21.1.12

Whenever an article is selected in Gnus summary buffer, the following
message is dumped to XEmacs's stdout/stderr. Is it something I should
be worry about? It does cause some slowness to generate the summary
buffer since the messages are generated for every article during the
summary creation process.

TIA.

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, apply, if, save-excursion, gnus-article-date-lapsed, gnus-treat-article, gnus-display-mime, gnus-article-prepare-display, gnus-article-prepare, gnus-summary-display-article, gnus-summary-next-page, gnus-mouse-pick-article, call-interactively, read-minibuffer-internal, byte-code, read-from-minibuffer, completing-read, iswitchb, iswitchb-entry, <compiled-function of unknown origin>, call-interactively]

-- 
/tonyl

Re: Strange message dumped to shell when article selected

[Karl Kleinpaste]

Tony Lam <Tony.Lam@eng.sun.com> writes:
> XEmacs 21.1.12
> Whenever an article is selected in Gnus summary buffer, the following
> message is dumped to XEmacs's stdout/stderr. Is it something I should
> be worry about?
> Comparison between integer and character is constant nil (?0 and -1)

You're running an XEmacs compiled with debugging enabled.  I believe
this particular warning message has been excised in the 21.2 tree, but
I wouldn't be surprised if it's still there in 21.1.  Recompile with
--debug=none and it should go away.

Re: Strange message dumped to shell when article selected

[Karl Kleinpaste]

Tony Lam <Tony.Lam@eng.sun.com> writes:
> Comparison between integer and character is constant nil (?0 and -1)

Having just snooped around a bit, I do find that the warning you see
is from XEmacs/src/data.c in function eq_with_ebola_notice().

If you can't afford to use --debug=none, then you could instead add an
"#if 0" around the relevant pointless scribbling.  Either way, you'll
have to recompile, of course.