Nah, please make it configurable and ctrl+f then could be the default.

The search field is private to KCharSelect in kdeui, I don't think kcharselect
can reach in and set focus on it without KCharSelect exposing it.

kdelibs/kdeui/widgets/kcharselect.cpp line 298 defines Ctrl+L to give focus to
the search line. This shortcut is not overridden by KCharSelect, and is usable.
However, the shortcut is not shown to the user in any way.

This bug is invalid.

I agree that Ctrl+F is more convenient in KCharSelect, but may clash with other
function in other softwares which use this widget.

OK. I changed the code to use KStandardShortcuts. Now the shortcuts should be
what the user expects. I think there is more to be done.

David and me had a little discussion about the usage of QShortcut in that code.
I said it's wrong. David said otherwise. I still think KCharSelect should not
use QShortcuts in KDE code outside of clear dialog scope. The shortcuts will
not show up in the "configure shortcuts" dialog, they are invisible for the
user and they are subject to trigger shortcut conflicts because the shortcuts
editor doesn't know about them.

Mike

All keyboard shortcuts should show in the configure shortcuts, that's the whole
point.
I don't see any benefit in configurable shortcuts if I cannot configure them
really.

Solved with revision r863397 in trunk. The shortcuts now properly show up in
the shortcut editor dialog.