Rik Kabel <rik(_at_)netcom(_dot_)com> writes:
...
Care must also be taken in condition lines which have a $ flag, and
are therefore parsed according to sh parsing rules (under which, for
example, multiple consecutive spaces and tabs may be treated as a single
space). There is also a warning about the way leading whitespace on
Not quite. To quote the procmailrc(5) manpage:
$ Evaluate the remainder of this condition according to
sh(1) substitution rules inside double quotes, skip
leading whitespace, then reparse it.
Whitespace is therefore never compressed inside of the resulting
expansion, though leading whitespace is stripped. (Actually, it's
more like substitution rules inside a here-doc, as double quotes aren't
special.)
continued regular expression condition lines is handled. It is handled
differently when both inside quotes and subject to a $ flag than at
other times.
I'm not sure I understand what you're saying here: conditions are never
"inside quotes". Can you give an example?
Philip Guenther