https://bugs.kde.org/show_bug.cgi?id=387618
avlas <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from avlas <[email protected]> --- (In reply to davidblunkett from comment #2) > This is nonsensical -I understand that unspecific keys are not very useful > but that is an issue for the user and shouldn't be enforced by the interface. > > I need to do a 2 letter search that will uniquely identify 3 emails out of > 1000 but this is blocked whereas there there are lots of longer strings that > will be found in every single email yet these are allowed. > > This is a poor policy and should be removed. I agree with this comment. Think for instance when looking for country codes, such as UK (also being sensitive to case would help for e.g. US) Perhaps the logi goes like this: searching 1 or 2 letters is very computationally demanding, and most of the time a user will search words of >= 3 letters anyways, so the user won't like the search process to be unresponsive after introducing the 1st or 2nd letter. If that would be the problem, could the search algorithm impose a delay to retrieve matches when only 1 or 2 letters are introduced? Would that be a good compromise solution? -- You are receiving this mail because: You are watching all bug changes.
