At 5:02 PM EDT on May 26 Rob Reid sent off:
> At 5:00 PM EDT on May 26 Anton Graham sent off:
> > Both of these revolve around the use of sig-dashes.
> >
> > First, I have a corrspondent who (despite protests) uses the ``-- ``
> > sequence to separate his message from the text he is replying to.
>
> Sounds pretty perverse. Maybe you could convince him (and only him) that the
> proper "sig separator" sequence is really -*- or something?
>
> > Needless to say, this causes mutt to syntax hilight the first
> > paragraph of his reply as a signature. Perhaps a check to see how
> > many lines remain after the sig-dashes would be helpful in dealing
> > with situations like this. Say, for example, > 10 lines remain after
> > sig-dashes means it's not a sig? This would still provide enough
> > space for the cast majority of over-long sigs.
Just had a better idea...I have this
# Correct wrong sig-dashes
:0 fBw
* ^--$
| sed -e 's/^--$/-- /'
in my .procmailrc, (probably from
http://www.math.fu-berlin.de/~leitner/procmail/procmailrc ) which you could
adapt to something like
:0 :
* From annoying\.correspondent
| sed -e 's/^-- $/**Badly quoted text starts now!** /'
I haven't tested it and I'm not a procmail guru, but something vaguely
resembling that should work.
--
Linux: The OS people choose without $200,000,000 of persuasion.
-- Mike Coleman
Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/
PGP Key: http://astro.utoronto.ca/~reid/pgp.html
