pdabrowski added a comment.
In D26718#595756 <https://phabricator.kde.org/D26718#595756>, @davidedmundson wrote: > I don't want us to make krunner autostart. It's a hack, not a fix. I'm gonna play devil's advocate here :) If having an already running KRunner service is a hack, then why not terminate it each time after its job is done - and restart on request each time it is needed again? Bug #416145 says exactly this: "When krunner is invoked again during the same session it will work correctly." So you oppose preloading of KRunner service, but accept it continuing to run forever awaiting its next use. I don't find this consistent. IMHO (correct me if I'm wrong!): Something that is supposed to act immediately should be preloaded (sure: it may be a lighter version). Currently to show the KRunner window for the first time: - a call is made to D-Bus - which detects there is no KRunner service running - so it executes the KRunner binary - which then builds its UI - shows itself - and only then accepts user input This can't work fast. Meanwhile all user's keystrokes go to previously active window. REPOSITORY R120 Plasma Workspace REVISION DETAIL https://phabricator.kde.org/D26718 To: pdabrowski, #plasma, #plasma_workspaces, davidedmundson, ngraham, broulik Cc: plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart
