Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Pre-Processed maiil splitting under Gnus?
Date: 12 Jan 1999 17:38:21 +0100	[thread overview]
Message-ID: <kigww2sh2f6.fsf@jagor.srce.hr> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "12 Jan 1999 17:02:07 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Asymptotically Approaching Relaxation <feoh@cosmic.com> writes:
> 
>   > I'm seeing a total performance turnaround once I re-wrote my .gnus
>   > file and minimized the length and complexity of the regexes I'm
>   > filtering on.
> 
> Ah.  Why didn't I think of this?  Since the Day of the
> Posixification of Regexes, regex matching has been rather slower for
> a number of regexes; and I'm not sure whether the fact that they're
> posixly correct now should be considered a Good Thing...

Strange.  Two remarks, though (none of which is meant to argue with
you):

1) As demonstrated by Tom Lord, GNU regex (which both Emacsen use) is
   still not POSIX.

2) Why are there, at least in XEmacs, two sets of functions, posix-
   regexp functions, and "normal" regexp functions?  Also, the
   internal code has various posix-p flags that apparently specify
   whether POSIX behaviour is desired.  I though the reason for
   duplicate functionality was to gain speed in the non-POSIX (the
   more usual) case.


  reply	other threads:[~1999-01-12 16:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <feoh@cosmic.com>
1999-01-11 22:08 ` Asymptotically Approaching Relaxation
1999-01-11 23:51   ` Richard Coleman
1999-01-12  7:00     ` Asymptotically Approaching Relaxation
1999-01-15  0:53     ` using multiple Summary buffer formats Alfred J Correira
1999-01-15 10:23       ` Kai.Grossjohann
1999-01-15 10:35         ` Lee Willis
1999-01-15 11:13           ` Kai.Grossjohann
     [not found]             ` <lzww2o21ez.fsf@landlord.gbdirect.co.uk>
     [not found]               ` <vaf7luon2dv.fsf@ramses.cs.uni-dortmund.de>
1999-01-15 12:34                 ` Kai.Grossjohann
1999-01-15 13:04                   ` Lee Willis
1999-01-15 14:27                     ` Karl Kleinpaste
1999-01-19 14:54                       ` Jack Vinson
1999-01-19 15:15                         ` Lee Willis
     [not found]   ` <m3iuedcuua.fsf@peorth.gweep.net>
1999-01-12  7:57     ` Pre-Processed maiil splitting under Gnus? Asymptotically Approaching Relaxation
1999-01-12 16:02       ` Kai.Grossjohann
1999-01-12 16:38         ` Hrvoje Niksic [this message]
1999-01-12 17:00           ` M-x gnus-filter-mail-at-warp-10 (was: Re: Pre-Processed maiil splitting under Gnus?) Asymptotically Approaching Relaxation
1999-01-12 17:35             ` Kai.Grossjohann
1999-01-12 18:42               ` Asymptotically Approaching Relaxation
1999-01-13 22:35                 ` Kai.Grossjohann
1999-01-12 20:49             ` M-x gnus-filter-mail-at-warp-10 (was: " Jari Aalto+mail.procmail
1999-01-13 22:32               ` Kai.Grossjohann
1999-01-13 23:21                 ` Hrvoje Niksic
1999-01-12 17:21           ` Pre-Processed maiil splitting under Gnus? 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=kigww2sh2f6.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).