From: Juha Autero <Juha.Autero@iki.fi>
Subject: Re: Problems with Oort Gnus 0.18 and XEmacs 21.4.6.
Date: Thu, 24 Apr 2003 23:39:21 +0300 [thread overview]
Message-ID: <87wuhjmxza.fsf@jautero.no-ip.org> (raw)
In-Reply-To: <ilud6jcovyj.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> 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.
Now I managed to debug it and seem to have found the problem. The
regexps that remove spaces are wrong. They use '*' which matches also
zero occurances. That causes regexp to always match and there is an
infinite loop.
--
Juha Autero
http://www.iki.fi/jautero/
Eschew obscurity!
next prev parent reply other threads:[~2003-04-24 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 21:45 Juha Autero
2003-04-24 13:40 ` Simon Josefsson
2003-04-24 20:39 ` Juha Autero [this message]
2003-04-24 21:48 ` Juha Autero
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=87wuhjmxza.fsf@jautero.no-ip.org \
--to=juha.autero@iki.fi \
/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).