[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 59158] Add filter action that creates/triggers an event
From:       Karl-Heinz Zimmer <khz () kde ! org>
Date:       2003-05-30 22:46:02
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=59158     




------- Additional Comments From khz@kde.org  2003-05-31 00:46 -------
Subject: Re:  Add filter action that creates/triggers an event

On Saturday 31 May 2003 00:26, Mitsu Hadeishi wrote:
> http://bugs.kde.org/show_bug.cgi?id=59158

> 00:26 ------- I made a patch to KMail HEAD that allows you to disable new
> mail notification for specific folders, which I think is a better solution
> than the above.  See bug 57908 for more details.  I don't believe my patch
> has been integrated into KMail HEAD yet.  I am using a version of KMail
> 1.5 which has my feature added into it on my own system --- it's a great
> feature.
>
> I think this is more useful than doing it on a per-filter basis.

Mitsu, your feature sounds interesting, but please tell us *why* you think
it is more useful than doing it on a per-filter basis.
To me your feature seems to serve another purpose - so it is hard to under-
stand that it might be 'more useful': this is a bit like saying that an
apple is more useful than a banana.  :-)

example: If I want to be notified of all mails coming form abc@def.org
- - no matter which mailing list this person is writing to - then it might
be a good idea to use a per-filter solution, and (in this case) your
aproach might be not so good...

Karl-Heinz
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]