Hi,
from time to time I get these kinds of reply from the mailing list.
Are there other “victims” as well?
Cheers
robert
---------- Forwarded message ----------
From: Mail Delivery S. [email protected]
Date: Wed, Nov 16, 2011 at 9:02 AM
Subject: Undelivered Mail Returned to Sender
To: [email protected]
This is the mail system at host carbon.ruby-lang.org.
I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
[email protected]: Command died with status 9:
"/usr/local/bin/spamassassin |/usr/share/fml/fml.pl
/var/spool/ml/ruby-talk
". Command output: Nested quantifiers in regex; marked by ← HERE in
m/^CAM9pMnPf5O=CqBnE-++ ← HERE k7Sadv8gu9XaQ2c3JyqCfCBWdb7=BDw/ at
/usr/share/fml/fml.pl line 1844, <LOOKUP_TABLE> line 1.
Final-Recipient: rfc822; [email protected]
Action: failed
Status: 5.3.0
Diagnostic-Code: x-unix; Nested quantifiers in regex; marked by ← HERE
in
m/^CAM9pMnPf5O=CqBnE-++ ← HERE k7Sadv8gu9XaQ2c3JyqCfCBWdb7=BDw/ at
/usr/share/fml/fml.pl line 1844, <LOOKUP_TABLE> line 1.
---------- Forwarded message ----------
From:Robert K. [email protected]
To:[email protected]
Date:Wed, 16 Nov 2011 09:02:38 +0100
Subject:Re: Regex to divide document into sections?
On Wed, Nov 16, 2011 at 6:53 AM, Intransition [email protected]
wrote:
The actual content shouldn’t really matter. Sorry, I should have been more
clear about that. The key pattern that the regexp would have to depend on is
the indentation.
I would think there is a way, but I’ve tried a few times to get this and
never quite get it. Maybe this is something that regexp’s just can’t do?
If the lowest indentation level can have varying numbers of spaces
then I believe it will be really tricky do solely do it with a regexp
because you need a capturing group to detect the first indentation
length in order to be able to reuse it to match subsequent lines. I
think a line by line solution is actually the best here.
Kind regards
robert
–
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/