Bug 77878 - strip whitespace from quick search query
Summary: strip whitespace from quick search query
Status: RESOLVED DUPLICATE of bug 161901
Alias: None
Product: kmail
Classification: Applications
Component: search (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2004-03-17 22:33 UTC by Daniel Naber
Modified: 2011-05-18 14:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Naber 2004-03-17 22:33:41 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

I suggest leading/trailing whitespace is removed
before the quick search query is evaluated. This will help avoid confusion if someone enters e.g. two spaces but the quick search has no focus anymore -> it would look like there's no mail in the folder, but there are just 0 matches.
Comment 1 Dan Allen 2004-03-18 03:45:53 UTC
+1

Seems reasonable to me.

Comment 2 Ingo Klöcker 2005-01-11 02:11:02 UTC
This would make it impossible to look for a certain word, e.g. " or ". Maybe instead of stripping whitespace it could be visualized somehow.
Comment 3 Maciej Pilichowski 2008-05-10 16:00:27 UTC
I rather opt against this wish. 

There are two issues here:
* visual readability -- removing spaces does not solve the problem, I would suggest adding small marker at the end of the line, something like this:
how many spaces at the end?   <|

* need for more powerful query (searching for whole words as Ingo showed) -- it should be solved in "find messages", after all it is _quick_ search so it shouldn't be too much complex
Comment 4 Maciej Pilichowski 2008-05-10 16:23:56 UTC
ad.#2, whole words:
http://bugs.kde.org/show_bug.cgi?id=161901
Comment 5 Björn Ruberg 2009-12-19 00:38:35 UTC
Suggesting as a junior job.
Comment 6 Christophe Marin 2011-05-18 14:55:42 UTC
merging with 161901

*** This bug has been marked as a duplicate of bug 161901 ***