> Evolution CVS has a means of piping messages to a process and getting > back (via exit code of said process) a value which can be compared > against to find whether or not you want to filter that message.
Ok, I don't know much about the semantics of said feature because I only once tried a recent CVS version very short a while ago. > At some point we plan on adding a scripting engine to Evolution so that > users can implement their own "wouldn't this be cool" features > themselves, so I'd rather not add Perl now only to remove it later in > favour of some other scripting language. I'd prefer to do it once and do > it The Right Way (tm). Maybe you could have a look at The Gimp, which does it in some way that seems easily extensible with respect to language bindings. Probably something to do with their procedure database, but I'm not sure. Might well be overkill for the more simple tasks of mail management (well, I think its more simple than image manipulation anyway). But I can see that you wouldn't want to add some perl things -- most users would probably never use that "baggage". johannes _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
