I often use the quick filter bar on top of the message list to filter for keywords in subject or from. This however does not work properly anymore: most often only few messages with the given keyword in the subject or FROM are found - or none at all. Reproducible: Always Steps to Reproduce: 1. Enter a keyword in the quick search bar on top of the message list 2. Count the found e-mails 3. Compare to the e-mails actually in the message list, and note the difference Actual Results: Too few messages or none at all are shown. Expected Results: All messages containing the keyword should be shown. I am not sure in how far Nepomuk, Baloo or anything else runs on my system properly. Since there are hardly any information available how to properly configure (or even install) baloo with KDE 4.13 I cannot check. Additionally, I hardly need e-mail indexing since many e-mails are encrypted anyway.
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. ***