From: "David W. Tamkin" <dattier(_at_)ripco(_dot_)com>
Dallman has a point: not everyone, despite strong advice, uses a
non-csh shell for procmailrc actions with shell metacharacters. Maybe
the implicit local lockfile name code could deal with >>! by stripping
the exclamation point and adding $LOCKEXT. Any chance that that would
break existing recipes that append to files whose names begin with
exclamation points? Would it be necessary to check first whether
$SHELL's antepenultimate character is `c'?
It also occurred to me that even ">" (and ">!" under C-shell-family
syntax) could result in file corruption without a lock. Or is one
simply expected - as in the good old days before local lock recognized
">>" - to explicitly provide for the lock by name?
ObReminiscenses, I mentioned remembering when Stephen added the code for
locking ">>". I didn't say, but might as well do so now, that I think
it might actually have been I who first asked on this list about how
one might compress saved folders. I suspect it was David Tamkin - but
it could have been Stephen, or anyone - who first shot back with the
"| gzip -fc >> file" response that is now a staple in man procmailex.
(How far back do the archives, go, anyway? I'd go look, but I'm not
someplace where that's convenient right at this moment.) This would
have been around 1993 or 1994.
--
"dman+noacks(_at_)nomotek(_dot_)com" slides around the auto-ack
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail