From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: Simplifying split-fancy rules
Date: Wed, 29 Oct 2003 14:40:41 -0500 [thread overview]
Message-ID: <874qxromrq.fsf@everett.mit.edu> (raw)
In-Reply-To: <76brs0j8o9.fsf@newjersey.ppllc.com> (Jake Colman's message of "Wed, 29 Oct 2003 11:44:06 -0500")
Jake Colman <colman@ppllc.com> writes:
> Can the following split-fancy expressions be combined in someway since they
> all end up in the same place?
>
> (any "ding@gnus.org" "INBOX/Emacs/ding")
> (any "ding@gnus.com" "INBOX/Emacs/ding")
> (any "ding@hpc.uh.edu" "INBOX/Emacs/ding")
> (any "ding@ifi.uio.no" "INBOX/Emacs/ding")
You could use (regexp-opt '("ding@gnus.org" "ding@gnus.com" "ding@etc."))
to get a single regexp that matched all of those strings.
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next prev parent reply other threads:[~2003-10-29 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 16:44 Jake Colman
2003-10-29 17:36 ` Reiner Steib
2003-10-29 19:40 ` David Z Maze [this message]
2003-10-29 19:59 ` Jake Colman
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=874qxromrq.fsf@everett.mit.edu \
--to=dmaze@mit.edu \
/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).