> IMO that's the way to make a program bloated: add options that have
> a very limited usage.
Well, you're right.
> What I would prefer (and have asked for several times):
> import/export filters to/from a .ini-like text file.
I vote for this! This really could solve my problem and could solve
other problems, too -- for example, I can have a good overview on all
my filters, I can see when and how do they overlap, and so on.
Thank you, Wolfgang.
> and one that would involve a simple decision-based language, like:
Oh, MaXxX, you can't imagine how long I'm dreaming of that. The
examples you're mentioning are perfect, only let me give a small
addition:
IF subject CONTAINS "earn money" {
MOVE TO /Trash
MARK AS Read
QUIT
}
I added a single QUIT which causes TB to end dealing with the "earn
money" message. Omitting it, TB should go on with the further code.
Considering the full filter code as one large program code may lead to
very sophisticated filters, even much better sophisticated than
anything what we can do now -- with a developed set of instructions,
of course.
The only problem with your idea is that -- will it be ever realized?
:(
La'ng Attila D. <[EMAIL PROTECTED]> <http://lad.rentahost.net>
--
______________________________________________________
Archives : <http://tbbeta.thebat.dutaint.com>
Moderators : <mailto:[EMAIL PROTECTED]>
Unsubscribe: <mailto:[EMAIL PROTECTED]>
You are subscribed as : archive@jab.org
