Re: Problems with Oort Gnus 0.18 and XEmacs 21.4.6.

[Simon Josefsson <jas@extundo.com>]

Juha Autero <Juha.Autero@iki.fi> writes:

> I've been lately having problems with Oort Gnus and XEmacs 21.4.6.
> I have several nnrss groups and nnrss.el started complaining that 
> Symbol's function definition is void: replace-regexp-in-string
>
> That seemed easy enough since XEmacs 21.4.6 doesn't have
> replace-regexp-in-string, but  gnus-util.el defines
> gnus-replace-in-string that does the same thing, but has arguments in
> different order, which crashed my XEmacs. After fixing that XEmacs no
> longer crashes. It just eats up CPU. I gave up after 10 minutes and
> tried to debug with M-x load-library nnrss and M-x debug-on-entry
> nnrss-node-text (where replace-regexp-in-string were). And what do you
> know, now it decides that information stored about nnrss groups is
> wrong and asks URL to search group and complains "Wrong argument type:
> stringp, ((description "<description of rss group>"..." or something
> like that after I give the URL. Since I have no idea how to delete 
> information stored by nnrss, I decided to give up and complain instead
> of sending a patch.
>
> BTW. sieve.el seems also have replace-regexp-in-string, but luckily I
> don't use that one.

I made both files not use r-r-i-s, which seems to be the correct
solution (Emacs 20 doesn't have r-r-i-s either), but I don't know the
solution to the two other problems.  Perhaps the implementation of
gnus-r-r-i-s is buggy when the NEWTEXT is ""?  Edebugging really
should work.  Perhaps instead of debugging, you could insert a
(message "foo: %s" text) statement in the function and then try to
evaluate gnus-r-r-i-s manually on it to see why it eats CPU.