From: Alexandre Oliva <oliva@dcc.unicamp.br>
Subject: RESTRICT for splits: (FIELD VALUE [- RESTRICT [...]] SPLIT)
Date: 04 Jul 1999 22:52:39 -0300 [thread overview]
Message-ID: <oreminc17c.fsf@cupuacu.lsd.dcc.unicamp.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
This is a new implementation of RESTRICT clauses in fancy splits.
It's much simpler than the one I posted before, but it's reasonably
easy to prove that, if restricts are not used, it is equivalent to the
currently installed code.
However, because the multi-match feature is not included in this
patch, it may fail to handle certain cross-posting cases. For
example, if the split is `(any "foo"- "x-foo" "foo.list")' and the
header line that first matches `foo' is: `To: foo, x-foo', this split
won't be used, because `x-foo' will be matched and restrict will
match, but no other occurrences of `foo' will be looked for.
The patch for the lisp code is the first attachment. The second
attachment is a re-post of the patch for the .texi documentation.
--
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
[-- Attachment #2: restrict.patch --]
[-- Type: application/x-patch, Size: 3804 bytes --]
[-- Attachment #3: restrict-docs.patch --]
[-- Type: application/x-patch, Size: 1693 bytes --]
next reply other threads:[~1999-07-05 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-05 1:52 Alexandre Oliva [this message]
1999-07-05 2:37 ` 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=oreminc17c.fsf@cupuacu.lsd.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
/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).