Gnus development mailing list
 help / color / mirror / Atom feed
From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: nnmail-split-it
Date: 03 Feb 1997 17:29:24 -0800	[thread overview]
Message-ID: <r9q3evdpde3.fsf@snowking.cs.washington.edu> (raw)
In-Reply-To: <rvraixqxkn.fsf@sdnp5.ucsd.edu>

>>>>> David Moore writes:

 > 	And a much better fix would be to preparse the message headers,
 > to allow much faster comparisons, as it's really slow currently with
 > lots of split rules.

Hmm.  I wrote some elisp code to do splitting like this.  I didn't
distribute it because:

* I realized that the bottleneck was disk access time (over NFS).

* I heard that elisp operations on buffers tend to be faster than
  operations on strings.  (Tracking start/end points would help this,
  but either make it less useful to me or more complex.)

It generates a alist of headers, unwrapping lines within headers and
separating values from duplicate headers with "\n".  You then match
with a header or multiple ones concatenated (very useful, for me at
least).  I never compared them with the default split rules, but I'm
fairly sure that this code is tight enough that it's very unlikely to
be a bottleneck.

If you're interested in the code, drop me a line.

--Paul


  reply	other threads:[~1997-02-04  1:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-02 22:06 nnmail-split-it Johan Danielsson
1997-02-03 23:28 ` nnmail-split-it David Moore
1997-02-04  1:29   ` Paul Franklin [this message]
1997-02-04  1:55     ` nnmail-split-it Lars Magne Ingebrigtsen
1997-02-04  4:35       ` nnmail-split-it David Moore
1997-02-04  6:16         ` nnmail-split-it anonymous
1997-02-04  8:37       ` nnmail-split-it Per Abrahamsen
1997-02-04 18:05         ` nnmail-split-it David Moore
1997-02-04 19:58           ` nnmail-split-it Lars Magne Ingebrigtsen
1997-02-05  6:44             ` nnmail-split-it Paul Franklin
1997-02-05  8:24           ` nnmail-split-it Per Abrahamsen
1997-02-04  0:46 ` nnmail-split-it Lars Magne Ingebrigtsen

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=r9q3evdpde3.fsf@snowking.cs.washington.edu \
    --to=paul@cs.washington.edu \
    /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).