On 2009.02.10 18:16:00 +0000, LuKreme wrote:
On 10-Feb-2009, at 16:48, Alan Clifford wrote:
On Tue, 10 Feb 2009, Rem P Roberti wrote:
Does the piped condition have to be contained in curly braces?
That's
the question I'm having about syntax. If I do use the piped
condition,
how to I include it within the recipe?
No, assignment to a variable does not have to go in a recipe at all.
While this is true, in the case at hand, the assignment only wants to
be triggered when conditions are met. In that case the syntax as I
posted is correct:
:0
* condition
{ DUMMY=`command` }
(NB: the spaces after and before the { } are NOT optional)
This can also be written as
:0
* condition
{
DUMMY=`command`
}
Gentlemen...I don't want to want to appear overly dense, but I'm
thinking that as a newbie I'm in a bit over my head. Nothing I try
works. Now, I do know that if I run...
mplayer ~/Audio/notify.wav
...the sound plays fine. I just don't seem to be able to incorporate
that into a recipe. Perhaps, if I provide you with an existing recipe
you could show me how the above could be incorporated. Here 'tis:
:0
* ^TO_rem(_at_)remdog(_dot_)net
$HOME/Mail/inbox/
Sorry to beat on this, but I'm having a hard time wrapping my mind around
the fine points.
--Rem
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail