https://bugs.kde.org/show_bug.cgi?id=387618
Huanyu Liu <1293660...@qq.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1293660...@qq.com
--- Comment #17 from Huanyu Liu <1293660...@qq.com> ---
It is 2025 now, and the issue still persists. It is especially annoying when
searching for CJK characters, during which 2 characters (or even 1 character)
should suffice most of the time.
I think the main motivation for this "feature" is to prevent hitting too many
search results, instead of reducing system resource consumption, because
finding out all 10-letter results (a more strict criterion) should consume more
resources than finding out all 2-letter results (a looser criterion).
Therefore, we can adopt other measures based on the number of search results.
For example, when doing a 2-character search, if the number of results hits a
threshold (say 100), then the search process is paused, and the user is
prompted whether to continue searching or not. Alternatively, this threshold
can be set to 0, so the user needs to initiate a 2-character search explicitly.
Or better, certain ranges of characters (such as CJK ideographs) can be
pre-defined, so that the 3-character restriction does not apply at all if the
search string contains characters in these ranges.
All in all, the user should have the choice to do quick a search with less than
3 characters.
--
You are receiving this mail because:
You are the assignee for the bug.
