Version: 1.5 (using KDE 3.1.0) Installed from: Mandrake Linux Cooker i586 - Cooker Compiler: gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk) OS: Linux (i686) release 2.4.21-0.13mdkenterprise When just looking at some complicated match patterns doesn't explain what a specific filter does "Checks header info for content-type and then moves it to the trash if it matches" or similar. Just a text box in the filter window.
Outlook does this. Mind you it doesn't do it well, but it is quite helpful to new users of mail filtering (and KMail's is quite powerful).
You know that you can give filters arbitrary names, right? If you wrote a filter yourself then you will surely know what it's supposed to do. So giving it a meaningful name shouldn't be a problem. Showing a textual description of a filter like "If content/type matches text/html then move to folder trash" would help a bit. But you'll have to admit that naming this filter "Dump HTML-only messages" is much better. Unfortunately the latter can't be done automatically.
Subject: Re: Filters should have comment fields to explain what they do On Friday 25 July 2003 04:06 am, you wrote: > You know that you can give filters arbitrary names, right? If you wrote a The "Rename" button at the very least, should be available in a right-click menu, but the comment field would add a HUGE amount of readibility to a very long filter. There's only so much you can rename a filter to to help explain it. This will be very useful in companies, where you have multiple filters that you didn't write yourself, but were pushed on you by your dept. I only know this, because it happened to my department. And there aren't really any reasons NOT to add comments, and a few good reasons to do it...
Ingo, I cannot agree with you. It is well know fact that writing a program is one thing, and reading it (one year later) is another. Commenting is a useful feature, and of course filters are not programming language, but putting there just regexp and even titling it properly is not everything. You could comment what the regexp does (or what was intended it should do). Btw. I would also add -- please add default comments for default filters. It is possibly to figure out which spam filter does what and when, but comment would ease that (and save some time).
Why didn't this bug ever get fixed? Seems like a big deal...
Because real life bites -- lack of time. If you had spare time a bit and could fix this issue your effort would be highly appreciated -- thank you in advance.
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.