https://bugs.kde.org/show_bug.cgi?id=459586
--- Comment #2 from Slavi <sl...@devture.com> --- (In reply to Natalie Clarius from comment #1) > It looks like in the specific example you cited, in all of the not very > relevant results "to" occurs inside one of the match words: "deskTOp", > "moniTOr", "auTOmatic", etc. So filtering out stop words in the sense that > an exact match with a common word like "to" or "the" shouldn't bring up the > result wouldn't help here since 1. it is not a word match but a substring > match, and always removing all results that contain "to" somewhere would be > a bad idea, 2. the problem would occur similarly with common sequences of > letters that don't correspond to any common words. > > I do agree though that the results you're showing don't make a lot of sense > for the query, so one possible solution would be to make the system settings > runner fire only when the match is longer than, say, 4 letters. I don't think people who search for "to" (only) will want to get a match for "moniTOr" or "auTOmatic". These substring match results also seem useless, don't they? I do not expect that doing a (insert search engine name) search for "car" would give me results for "myoCARditis" - that's completely irrelevant. Prefix-matches, maybe. Substring and fuzzy string matches, it seems pointless. -- You are receiving this mail because: You are watching all bug changes.
