Re: Sieve support?

[NAGY Andras <nagya@inf.elte.hu>]

On Thu, 01 Nov 2001, at 17:50, Simon Josefsson <jas@extundo.com> wrote:

> I don't think the automatically generated code should ever invoke
> "stop", since you may want to put Sieve code after the Gnus generated
> code block.  Do you agree?

Yes, that's why I would still prefer the elsif way.


On Fri, 02 Nov 2001, at 18:48, Amos Gouaux <amos+lists.ding@utdallas.edu> wrote:

> kg>     if foo {
> kg>         fileinto "bar";
> kg>         stop;
> kg>     }
>
> I've tended to do this for mailing list folder stuffing.  Main
> reason for it is out of paranoia that if I've got a vacation item at
> the bottom of the script, there's no way at all that a list or list
> admin will have to deal with it.

Well, you can set crosspost to nil, and add something like

else {
   # vacation stuff, storing in "mail.misc", etc
}

after the generated part.


How about a trade-off? :-) Let's introduce a new variable instead of
-crosspost, defining which control structures to use when building the
script?  Say,

gnus-sieve-script-flavour:
  if (default):  [if () { fileinto }]*, crossposting
  elsif:         `if ... [elsif () { fileinto } ]*', no crossposting, no stop
  stop:          [if () { fileinto; stop; }]*, no crossposting, with stop



Andras