From: Toby Speight <Toby.Speight@digitivity.com>
Subject: Re: `nnmail-split-fancy' regexp
Date: 07 Jul 1999 15:28:30 +0100 [thread overview]
Message-ID: <u673wfsa9.fsf@lanber.ansa.co.uk> (raw)
In-Reply-To: Alexandre Oliva's message of "Sun, 04 Jul 1999 21:18:44 GMT"
Alexandre> Alexandre Oliva <URL:mailto:oliva@dcc.unicamp.br>
0> In <URL:news:org134ru9z.fsf@cupuacu.lsd.dcc.unicamp.br>, Alexandre
0> wrote:
Alexandre> OTOH, it might break existing code that relies on the
Alexandre> existing format. In this sense, `.*' would be better.
Perhaps '*' might be best - a real regexp won't begin with '*', so
the software can distinguish it from true regexps for the traditional
splitter[1], and users won't be confused whether it's part of the
regexp for \& purposes.
[1] I have rules that require word boundaries at one end (like
".*@digitivity.com" to split work-related mail). I don't
expect users with similar rules to have to change them (to
".*@digitivity.com\\>" in my case) because the magic prefix
has changed Gnus's interpretation.
next prev parent reply other threads:[~1999-07-07 14:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-24 8:25 Petersen Jens-Ulrik (NRC/Tokyo)
1999-06-24 18:26 ` Per Abrahamsen
1999-06-25 7:52 ` Petersen Jens-Ulrik (NRC/Tokyo)
1999-06-25 9:48 ` Kai.Grossjohann
1999-06-25 10:28 ` Alexandre Oliva
1999-06-25 11:48 ` Kai.Grossjohann
1999-06-25 12:51 ` Alexandre Oliva
1999-06-25 9:42 ` Alexandre Oliva
1999-06-25 12:25 ` Per Abrahamsen
1999-06-28 17:33 ` Lars Magne Ingebrigtsen
1999-06-28 18:14 ` Aaron M. Ucko
1999-06-28 18:49 ` Per Abrahamsen
1999-06-28 19:11 ` Alexandre Oliva
1999-07-04 3:07 ` Lars Magne Ingebrigtsen
1999-07-04 21:15 ` Alexandre Oliva
1999-07-04 22:54 ` Alexandre Oliva
1999-07-07 14:28 ` Toby Speight [this message]
1999-07-07 17:38 ` Alexandre Oliva
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=u673wfsa9.fsf@lanber.ansa.co.uk \
--to=toby.speight@digitivity.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).