Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: gnus-split-references tweak
Date: Thu, 07 Feb 2002 02:59:56 +0100	[thread overview]
Message-ID: <m3adum2grn.fsf@defun.localdomain> (raw)
In-Reply-To: <m38za68fdy.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Wed, 6 Feb 2002 21:35:07 +0000 (UTC)")

prj@po.cwru.edu (Paul Jarc) writes:

> Jesper Harder <harder@ifa.au.dk> wrote:
>> prj@po.cwru.edu (Paul Jarc) writes:
>>> Hm.  It seems this actually isn't sufficient for recognizing them
>>> anyway.  I'm not sure what else would need to be changed, though.
>>
>> Maybe you also have to change the regexp in `gnus-parent-id':
>>
>>       (when (string-match "<[^> \t]+>\\'" references)
>
> Oops.  Yep, that works.  I'll commit it tomorrow if no one objects.
> -      (when (string-match "<[^> \t]+>\\'" references)
> -       (match-string 0 references)))))
> +      (when (string-match "\(<[^<]+[^< \t]\)[ \t]*\\'" references)
> +       (match-string 1 references)))))

You missed a couple of backslashes in the regexp, it should be

  "\\(<[^<]+[^< \t]\\)[ \t]*\\'"

But this regexp is rather expensive compared to the old one
(`gnus-parent-id' is called several times on each article).  Entering a
10k group was 15% slower for me.

I think this one:

      (when (string-match "\\(<[^>]+>\\)[ \t]*\\'" references)
	(match-string 1 references)))))

is more efficient -- the performance penalty was only about 2%.





  reply	other threads:[~2002-02-07  1:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 18:55 Paul Jarc
2002-02-06 20:50 ` Paul Jarc
2002-02-06 20:50   ` Jesper Harder
2002-02-06 21:32     ` Paul Jarc
2002-02-07  1:59       ` Jesper Harder [this message]
2002-02-07 16:30         ` Paul Jarc
2002-02-07 20:06         ` Paul Jarc

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=m3adum2grn.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).