On Wed, 23 Aug 2000, Dallman Ross wrote:
From: guenther+procmail(_at_)gac(_dot_)edu
I'll admit that one sentence description of the 'f' flag is not the
clearest. If someone has a better suggestion for what to put as the
description there on the procmailrc(5) manpage, please email me.
Well, yes, and I'll admit that the word "filter" so confused me that
I didn't really understand the simplicity of the -f flag until
six months ago. That is, I went 5 or 6 years confused because of
the lame description in the man page and the (what I consider to be)
misnomer.
Well, not a misnomer, but ambiguous. Let's address the ambiguity
directly.
For the 'man 5 procmailrc' page, I like the initially proposed text
as mentioned, but might also add a 'hint':
-------cut-------------
'filter' has become an overloaded term, but is used here the
traditional Unix textutils 'small competent tools' context. It
suggests 'filtering' tools, strung together by pipes, joining
stdout from a prior process to stdin of the next.
The use of the -f option will immediately modify a matching header
or body, as its target content, to a new form. Processing will then
proceed to the next matching rule in the .rcfile, if any, but will
reflect the changes of the 'filtering' rule at once.
--------cut ends--------
-- end ==================================
.-- -... ---.. ... -.- -.--
Copyright (C) 2000 R P Herrold
herrold+513(_at_)owlriver(_dot_)com NIC: RPH5 (US)
My words are not deathless prose,
but they are mine.
Owl River Company 614 - 221 - 0695
"The World is Open to Linux (tm)"
... Open Source LINUX solutions ...
info(_at_)owlriver(_dot_)com
Columbus, OH
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail