[prev in list] [next in list] [prev in thread] [next in thread]
List: sylpheed
Subject: [sylpheed:22974] Re: How to force thread break
From: Tommy Reynolds <Tommy.Reynolds () MegaCoder ! com>
Date: 2004-05-28 15:34:54
Message-ID: 20040528103454.453d815a.Tommy.Reynolds () MegaCoder ! com
[Download RAW message or body]
Uttered Bob Apthorpe <apthorpe-sylpheed@cynistar.net>, spake thus:
> > sed -r '1,/^$/s/^([iI]n-[rR]eply-[tT]o)|([Rr]eferences):/X-Former-\1:/'
> ITYM
> sed -r '1,/^$/s/^(([iI]n-[rR]eply-[tT]o)|([Rr]eferences)):/X-Former-\1:/'
I don't think the extra parens are necessary because of the
precedence of the "|" operator, but they do help transform the
original from line noise into something a bit more LISPy-readable.
Anyway, one mans cheese is another mans spoiled milk. You takes your
choice.
We seem to have gotten a bit far afield and are now OT.
Cheers!
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic