From: Neil Crellin <neilc@wallaby.cc>
Cc: ding@gnus.org
Subject: Re: nnmail-split-fancy question
Date: 03 May 1999 12:12:43 -0700 [thread overview]
Message-ID: <vb6k8uq7ys4.fsf@wallaby.tesserae.com> (raw)
In-Reply-To: Per Abrahamsen's message of "28 Apr 1999 21:58:36 +0200"
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> Neil Crellin <neilc@wallaby.cc> writes:
>
> > I figured I could do a simple rule like
> >
> > (to "^[^@]+$" "work")
>
> Try to reverse the test
>
> (| (to ".*@.*" ( ... has @, do normal processing ... ))
> "work")
Ugh. Just wanted to follow-up and thank Per. While this seems like an
ass-backwards way to do this to me, it works, and that's a lot better
than I'd managed myself. Many thanks, Per.
--
Neil Crellin <neilc@wallaby.cc>
prev parent reply other threads:[~1999-05-03 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-28 17:43 Neil Crellin
1999-04-28 19:04 ` Alexandre Oliva
1999-04-28 22:29 ` Justin Sheehy
1999-04-29 3:42 ` Alexandre Oliva
1999-04-29 7:51 ` Kai.Grossjohann
1999-04-28 19:58 ` Per Abrahamsen
1999-05-03 19:12 ` Neil Crellin [this message]
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=vb6k8uq7ys4.fsf@wallaby.tesserae.com \
--to=neilc@wallaby.cc \
--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).