Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: ding@gnus.org
Subject: Re: `nnmail-split-fancy' regexp
Date: 28 Jun 1999 16:11:28 -0300	[thread overview]
Message-ID: <oriu88nnrz.fsf@saci.lsd.dcc.unicamp.br> (raw)
In-Reply-To: Per Abrahamsen's message of "28 Jun 1999 20:49:02 +0200"

On Jun 28, 1999, Per Abrahamsen <abraham@dina.kvl.dk> wrote:

> amu@MIT.EDU (Aaron M. Ucko) writes:
>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

>> > Per Abrahamsen <abraham@dina.kvl.dk> writes:

>> > > How about using ".*" as the magic prefix instead?

>> > Sounds like a good idea.

>> Uhm, no.  As Alexandre Oliva observed a couple of days ago in

> And how is this relevant for what the magic prefix should be?

Ah, now I get it.  You're not suggesting that the feature is
unnecessary, you're just suggesting a different magic prefix.

Just a nit: in the case of \& substitutions, it isn't clear whether
the .* prefix is included in the match.  With the `[partial]'
implementation, it is not, which sounds reasonable, and probably
matches the users' expectations.  With `.*', it would not be
immediately clear whether `.*' is just a magic prefix or if it's
actually part of the regex.  Moreover, it would match everything up to 
the begining of the line, including the field name, which would break
the multi-match mechanism introduced in my last patch.  Let me try to
clarify.  Given a header line such as:

To: foo, bar

If we have rules for cross-posting that match both `foo' and `bar',
say `.*\(foo\|bar\)', `foo' will not be matched if `.*' is considered
part of the regexp, because the next backward-search would start just
before the previous match, i.e., just before the `To'.

So, even though `.*' appears to be much more intuitive, it is not
really that intuitive if you don't happen to know what's going on
behind the scenes, so I'd rather have a prefix that is clearly not
part of the regexp.  It might have been better to use a (cons 'partial
"regex") to denote partial matches...

-- 
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
{oliva,Alexandre.Oliva}@dcc.unicamp.br  aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists



  reply	other threads:[~1999-06-28 19:11 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 [this message]
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
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=oriu88nnrz.fsf@saci.lsd.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=ding@gnus.org \
    /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).