Summary: | Message list quick filter only finds few messages or none at all | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Roland Wolters <bugs> |
Component: | message list | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | asoliverez, montel, steve, t.kleindienst |
Priority: | NOR | ||
Version: | 4.13 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Roland Wolters
2014-04-14 10:06:44 UTC
I can confirm this behaviour (latest Kubuntu w KDE 4.13) I'm seeing the same behaviour (4.13.0 on OpenSUSE 13.1). It looks like the search (filter) method has changed. I used to be able to type "[" into the filter field and get messages that contain an open square bracket - used very often in mailing lists. Now I get nothing, although the emails exist. I wondered if it's being treated as a special character, perhaps by RegEx, but entering "\[" also yields no results. If I type "[interest", I get emails with the word interest - including emails with no square bracket. Searching for "nterest" yields no results. The new search method is definitely different. It ignores at least some non alphanumeric characters, and can only match partial words starting at the beginning of a word (same is true for numbers). The previous version could do these things. I experience the same. I assume this has to do with the fact, the search is now done by utilizing the baloo index table. As "[" is hardly going to be stored inside the index table the new search method will fail to look for "fragments" of words or single characters. Sadly I also was relying on this "powerful" ability to even filter fragments or single characters from the headers. Please test 4.13.1 I fixed this bug. Thanks! Will test it On 4.13.1, this particular bug no longer occurs for me. Thanks, Laurent. I can confirm that with the update to 4.13.1 this bug does not occur anymore. Thanks for taking care =) Just updated to 4.13.1 and the bug is gone... thanks *** Bug 334133 has been marked as a duplicate of this bug. *** |