Gnus development mailing list
 help / color / mirror / Atom feed
From: Niklas Morberg <niklas.morberg@axis.com>
Subject: Re: A RE: SV: AW: "collapser", anyone...?
Date: Wed, 04 Jun 2003 09:33:45 +0200	[thread overview]
Message-ID: <uof1e47qe.fsf@axis.com> (raw)
In-Reply-To: <hhn0gy39il.fsf@blah.pl> (Maciej Matysiak's message of "Wed, 04 Jun 2003 03:40:34 +0200")

Maciej Matysiak <phoner.ding@blah.pl> writes:

> the following regexp succeeded removing all the "re" variations from
> subject "Re[3]: Réf: Odp: SV[6]: Antw: blah", so i assume it works :)
>
> (setq message-subject-re-regexp
>       (concat
>        "^[ \t]*"
>          "\\("
>            "\\("
>              "\\([Aa][Nn][Tt][Ww]\\)\\|"              ; antw

Question: Are the parentheses really necessary? Isn't it
enough to say:

              "[Aa][Nn][Tt][Ww]\\|"              ; antw

I don't know.

>              "\\([Aa][Ww]\\)\\|"                      ; aw
>              "\\([Ff][Ww]d\\)\\|"                     ; fwd

The `d' is not always used. If it is, it is always (?) lower
case. Given that the `\\(' can be discarded this would be:

              "[Ff][Ww]d?\\|"                     ; fwd

>              "\\([Oo][Dd][Pp]\\)\\|"                  ; odp
>              "\\([Rr][Ee]\\)\\|"                      ; re
>              "\\([Rr]"                                ; réf
>                 (char-to-string (int-to-char '233))

Will this handle both upper and lower case (é and É)? I'm
not sure it's necessary, but since both `f' and `F' is
allowed maybe it should be there.

>              "[Ff]\\)\\|"
>              "\\([Ss][Vv]\\)"                         ; sv
>            "\\)"
>            "\\(\\[[0-9]*\\]\\)"
>            "*:[ \t]*"
>          "\\)"
>        "*[ \t]*"
>        ))

Breaking the regexp up made it much more readable, nice work.

Niklas




  parent reply	other threads:[~2003-06-04  7:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 23:23 Steinar Bang
     [not found] ` <hhhe7ak6ph.fsf@blah.pl>
2003-06-01 21:34   ` Steinar Bang
2003-06-01 21:51     ` Steinar Bang
2003-06-02  9:37     ` Niklas Morberg
     [not found]     ` <hhn0gy39il.fsf@blah.pl>
2003-06-04  7:33       ` Niklas Morberg [this message]
     [not found]         ` <hh8yshzuup.fsf@blah.pl>
2003-06-05  5:53           ` Steinar Bang
2003-06-05  6:48             ` Niklas Morberg
2003-06-09 20:26               ` Steinar Bang
2003-06-15 12:07                 ` Kai Großjohann
2003-06-20  5:17                   ` Steinar Bang
2003-06-15 12:06               ` Kai Großjohann
2003-06-05 17:25             ` A " Ted Stern
     [not found]               ` <hh7k7z4yeq.fsf@blah.pl>
2003-06-06 10:11                 ` lawrence mitchell
     [not found]                   ` <hhd6hpxel9.fsf@blah.pl>
2003-06-09 20:47                     ` Steinar Bang
2003-06-04 13:56       ` A RE: SV: " Johan Bockgård
2003-06-02 16:10   ` Randal L. Schwartz
2003-06-02 17:00     ` Lloyd Zusman
2003-06-02 17:05       ` Lloyd Zusman
2003-06-02 17:50         ` Harry Putnam
2003-06-03  6:12       ` Kai Großjohann
2003-06-03  6:16     ` Kai Großjohann
2003-06-04 15:56       ` Martin Thornquist
2003-06-03 11:49   ` Colin Marquardt
2003-06-03 12:13     ` Norbert Koch
2003-06-04  5:34     ` Oystein Viggen

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=uof1e47qe.fsf@axis.com \
    --to=niklas.morberg@axis.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).