Gnus development mailing list
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
Subject: gnus-cite-parse terribly slow on underscores
Date: Tue, 29 Jan 2002 09:35:19 +0100	[thread overview]
Message-ID: <m3u1t5h7w8.fsf@linux.local> (raw)

Hi Folks,

I am running Oort Gnus v0.05
XEmacs 21.4 (patch 4) "Artificial Intelligence" [Lucid] (i386-suse-linux, Mule) of Mon Sep 24 2001 on lhospital


Since upgrading to ognus I had a lot of problems with some mailing
lists and several other mails. 

Displaying these mails did take a really long time or locked up
totally. After a while I did get the pattern: They all had signatures
with a lot of underscores like e.g. yahoo adds.

I then did debug-on-quit and realised that gnus-cite-parse did lockup
in (looking-at gnus-supercite-regexp) or taking a long time in
(re-search-forward prefix-regexp (1- end) t).

Since I realised the underscore in the messages I examined
message-cite-prefix-regexp and gnus-supercite-regexp and noticed the
following common pattern: \(\w\|[-_.]\)+ and modified it to
\(\w\|[-.]\)+ and AHA! now it works.

I do not understand all the interactions, but at least in my xemacs _
is covered by \w and apparently this messes up looking-at and
re-search-forward. Perhaps it is a bug in my xemacs since its info
says:

,----
|    The XEmacs regular expression syntax most closely resembles that of
| `ed', or `grep', the GNU versions of which all utilize the GNU `regex'
| library.  XEmacs' version of `regex' has recently been extended with
| some Perl-like capabilities, described in the next section.
`----

Any insight?

Greetings
		Christoph





             reply	other threads:[~2002-01-29  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29  8:35 Christoph Rohland [this message]
2002-01-29 22:08 ` ShengHuo ZHU
2002-01-30 16:13   ` Christoph Rohland
2002-01-31  3:26     ` ShengHuo ZHU
2002-01-31  9:35       ` Christoph Rohland
2002-01-31 13:41         ` ShengHuo ZHU
2002-02-01 16:52           ` Christoph Rohland
2002-03-13 11:35   ` Christoph Rohland

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=m3u1t5h7w8.fsf@linux.local \
    --to=cr@sap.com \
    /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).