From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: fancy split regexp?
Date: Wed, 08 May 2002 17:51:51 -0400 [thread overview]
Message-ID: <87lmaui9zc.fsf@alum.wpi.edu> (raw)
In-Reply-To: <m38z6uctte.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Try this:
> ("Resent-To"
> "\\`\\(.*[^!#-'*+/-9=?A-Z^-~-]\\)?\\([!#-'*+/-9=?A-Z^-~-]*\\)@packages\\.qa\\.debian\\.org"
> "mail.debian.pts.\\2")
Oh dear god...
Can we somehow use re-search-forward for splitting? I tried this (the
above regexp), and it works in a scratch buffer, but not in the
fancy-split-rules. In fact, any time I try and use \\` it seems to
never match.
So, I gave up... (oh, and I found another header to match on ;):
(defun jmh::pts-group (base)
(goto-char (point-min))
(when (re-search-forward "^X-PTS-Package: \\(.*\\)$" nil t)
(concat base "." (match-string 1))))
and use it like so:
(: jmh::pts-group "mail.debian.pts")
probably slower, but I fell a lot better about it :)
Thanks for ideas,
--
Josh Huber
next prev parent reply other threads:[~2002-05-08 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 18:48 Josh Huber
2002-05-08 18:58 ` Bryan
2002-05-08 19:26 ` Josh Huber
2002-05-08 19:39 ` Paul Jarc
2002-05-08 21:51 ` Josh Huber [this message]
2002-05-10 9:46 ` Kai Großjohann
2002-05-10 15:23 ` Josh Huber
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=87lmaui9zc.fsf@alum.wpi.edu \
--to=huber@alum.wpi.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).