a few comments:
the default comparator is always "i;ascii-casemap", so it can be omitted
from the examples.
the actions and tests allows a list of flags to be specified as a space
delimited string. I assume this is intended to allow variable
references. e.g.:
set "s" "\\Answered Closed";
setflag "f" ["${s}", "\\Deleted"];
if hasflag "${f}" "${s}" ...
do we really need "setflag"? it is equivalent with "set", except it
allows some syntax checking of the arguments,
And possibily duplicate elimination and reordering.
but as you can see above,
it can't really do much of it statically anyhow.
Yes, but runtime checking is possible.
I think most users
will use "addflag" almost exclusively.
Without setflag I would expect to see stuff of the form
set "foo" "";
addflag "foo" "bar";
Whether or not this savings warrants an entire action is a judgement call.
Having implemented it I can say that for me at least supporting setflag only
amounted to about 15 additional lines of code and one additional table entry.
Ned