Now that there is the shift + return shortcut for activating the secondary action (see https://phabricator.kde.org/D3971), the tab key could behave like a down arrow key, which is easier to reach on the keyboard than the down arrow. The current behaviour of the tab key depends on whether there is a secondary action or not, which i find confusing. Holding tab moves with variable speed.
(In reply to kdeu from comment #0) > Holding tab moves with variable speed. ... and sometimes ends up selecting the entry and sometimes the action.
How are you supposed to reach the actions with your keyboard then? Tab is the designated key for "move to next control", whereas the arrow keys navigate in lists.
By pres(In reply to Kai Uwe Broulik from comment #2) > How are you supposed to reach the actions with your keyboard then? Press shift + return https://phabricator.kde.org/D3971 > action*s* Is it possible that there is more than one action? Haven't noticed that yet.
Shift + Return is not very discoverable, it's a shortcut to speed up workflows for those who know about it. Tab is how this works everywhere else. Yes, there can be multiple actions, the kill application runner for instance has actions for kill and term etc.
So is there a way to switch the keyboard shorcuts?
No.
It's hardcoded in a compiled source file?
Feel free to play around with the ResultsView.qml in /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/milou/ (might be in a slightly different location on your distribution), lines 122 and beyond handle tab key.
Thanks!