From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: fancy split regexp?
Date: Fri, 10 May 2002 11:23:31 -0400 [thread overview]
Message-ID: <87661wrpqk.fsf@alum.wpi.edu> (raw)
In-Reply-To: <vaf8z6sxrmh.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Sure, \\` only matches at beginning of buffer. But most mail
> addresses are not at the beginning of the buffer. For example, the
> header name comes before the address.
Ah, of course.
I guess my point still stands -- since we use re-search-backward it
makes regexps for matching addresses pretty disgusting...IMHO. Or,
near impossible.
Taking a peek at nnmail-split-it, I'm not ready to start screwing with
that code for fear in breaking people's split rules. =)
perhaps another time.
--
Josh Huber
prev parent reply other threads:[~2002-05-10 15:23 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
2002-05-10 9:46 ` Kai Großjohann
2002-05-10 15:23 ` Josh Huber [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=87661wrpqk.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).