Re: [Evolution] shell command filter not sending message?

[guenther <guenther rudersport de>]

cheers();

> > "Pipe to shell command" filter criterion pipes the mail via stdin. The
> > "Shell command" filter action doesn't.
>
> Well then ... that's a crapper. :(

Maybe a solution to that:

I suppose, 'if all criteria are met' will go through all the criteria in
the specified order and stop at the first false. So a solution would be
pure programmers logic:

  if ( i == 1 && ++i )
    cout << " i was 1 and now is 2 ";

Just define all criteria, that have to be met and as a last criteria set
'pipe message to shell command'. That will execute the command only,
when all other criteria are met. Action is void, so is the return status
of that shell command. ;-)

That should do the job, although it is not obvious for non programmers.


> I've got the script logging when it is called. It does get called. It
> isn't a shell script, it is a python script.

So what do you expect is interpreting the shebang line, if not a shell?
#!/usr/bin/python

I really assume, 'shell script' even could be 'wine msoffice'... >:->

...guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}