https://bugs.kde.org/show_bug.cgi?id=412271
--- Comment #4 from Christoph Feck <cf...@kde.org> --- The search field will only start its incremental searching when at least three characters are typed, or when Return is pressed. The idea is to avoid showing 10000+ results when starting to type with common letters such as 'e' or 'a'. KCharSelect doesn't implement the Unicode Emoji standard. It only works with codepoints. The reason a single space is sufficient for SMP characters is indeed a bug. It counts the number of UTF-16 codepoints, and Emoticon characters need two, so a single space raises it to three. In other words, if I fixed this bug, you would need to add two spaces. I doubt this is what you were after. Could you clarify how the decision when to start the incremental search could be improved? -- You are receiving this mail because: You are watching all bug changes.
