>>>>> On Fri, 9 Nov 2001 08:10:35 -0000,
>>>>> Ian Castle <[EMAIL PROTECTED]> (ic) writes:

ic> Well, the mechanism/interface is there. Allow "activate" to apply to more
ic> than one script.

ic> One way would be to have a subdirectory called "default" with symlinks to
ic> all the active scripts in the directory.

ic> The symlinks could be prefixed with a number "0001_myscript.script"
ic> "0002_mysecondscript" to allow ordering. You could introduce "up down"
ic> commands, or just let activate remove things from the list and append to the
ic> bottom. A bit clumsy without a gui. Or simply let the file names determine
ic> the order.

Okay, this is getting a little scary.  ;-)

ic> A second way would mean be to extend sieve with an "include" statement. So
ic> you would have "default" being include "[script1,script2,script3]";

But include from where?

If we had a script in 'user.billybob.lists.info-cyrus', then maybe
have:

 include ["user.billybob/default"]

???

Ugh, this is scary too.

ic> Anyway, this is perhaps orthogonal to the problem I am particularly
ic> interested in which is apply scripts to different folders - i.e. mapping
ic> scripts to the folder name space rather than the username space.

I'd agree with that.  Just being able to bind a script to a folder
would be a *huge* win, IMHO.

ic> So rather than thinking that "this script applies to this user" I am
ic> suggesting that we think "this script applies to this folder". Obviously, if
ic> the folder is "user.fred" then the statements are synonymous. However, we
ic> can use the second way to, obviously, refer to more than just folders of the
ic> category "user.something".

If you can set 'anyone p' to a folder, seems like you should be able
to bind a script to that folder....

-- 
Amos

Reply via email to