From: Lars Henriksen <Lars.Henriksen@netman.dk>
To: "Andrew J. Gray" <andrewg@gnu.org>
Cc: hatzis@juniper.net
Cc: help-gnats@gnu.org
Cc: yngve.svendsen@sun.com
Cc: pdm@zamazal.org
Subject: Re: Subject header matching--once again
Date: Mon, 03 Mar 2003 19:51:00 -0000 [thread overview]
Message-ID: <20030303194618.GB202487@teapot.netman.dk> (raw)
In-Reply-To: <200303021053.h22Arrn11407@localhost.localdomain>
On Sun, Mar 02, 2003 at 09:53:53PM +1100, Andrew J. Gray wrote:
> As I understand it the match-word-constituent operator (\w) is not
> meant to work inside matching lists. I am looking at the "info"
> documentation included with the regex 0.12 (available from
> http://ftp.gnu.org/pub/gnu/regex/regex-0.12.tar.gz). In the "List
> Operators" node it says most characters lose any special meaning
> inside a list.
>
> I think the closest equivalent that works in a list is the alnum
> character class. Using this the regular expression would become:
>
> \\<(PR[ \t#/]?|([-[:alnum:]_+.]+)/)([0-9]+)
>
> Do you think this is a satisfactory replacement for \w?
Absolutely. I have made a rudimentary test that worked OK.
The documentation should then have
\<(PR[ \t#/]?|[-[:alnum:]+.]+/)[0-9]+
in file p-usage.texi. I think that the text-capturing parentheses should
be left out for clarity.
Are you aware that Yngve has committed the documentation changes from
my patch already?
Regards
Lars
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-03-03 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 21:40 Lars Henriksen
2002-11-04 11:31 ` Mel Hatzis
2002-11-04 15:41 ` Lars Henriksen
2002-11-06 21:43 ` Lars Henriksen
2002-11-09 3:26 ` Mel Hatzis
2002-12-02 14:45 ` Lars Henriksen
2002-12-17 6:38 ` Yngve Svendsen
2003-03-02 11:57 ` Andrew J. Gray
2003-03-02 20:47 ` Mark D. Baushke
2003-03-03 20:22 ` Lars Henriksen
2003-03-03 19:51 ` Lars Henriksen [this message]
2003-03-09 2:33 ` Andrew J. Gray
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=20030303194618.GB202487@teapot.netman.dk \
--to=lars.henriksen@netman.dk \
--cc=andrewg@gnu.org \
--cc=hatzis@juniper.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).