https://bugs.kde.org/show_bug.cgi?id=526442
--- Comment #3 from ddnn <[email protected]> --- (In reply to ddnn from comment #2) > (In reply to Nicolas Fella from comment #1) > > Our shortcut system is designed to launch desktop files and the config file > > reflects that. We are not going to change that, sorry. > > Thanks for the quick response. > I will take a little while to respond fully. But my short response is that > for custom shortcut commands (with launch arguments or leading to a binary > file that is not "installed"), it is a redundant effort to have KGlobalaccel > create yet another file. Especially since the feature I am asking for > already exists in the same file (kglobalshortcutsrc), as can be seen with > Spectacle below. So, as a compromise, I am asking that we at least keep > custom commands created through "Add New > Command or Script..." in one file > - kglobalshortcutsrc. > > [services][org.kde.spectacle.desktop] > ActiveWindowScreenShot=none > CurrentMonitorScreenShot=none > FullScreenScreenShot=none > OpenWithoutScreenshot=none > RecordRegion=none > RecordScreen=Meta+Shift+Print > RecordWindow=Meta+Alt > RectangularRegionScreenShot=none > WindowUnderCursorScreenShot=none > _launch=none Just realised that my Spectacle example might not help, so instead (since I can't edit what was said). For command shortcuts, the full command is already within kglobalshortcutsrc at the _launch field. Examples: [services][net.local.mullvad-exclude-2.desktop] _launch=Meta+Ctrl+F [services][net.local.firedragon.desktop] _launch=Meta+Shift+F The .desktop file that KGlobalaccel generates in .local/share/applications duplicates this with no additional functional data since the display name can already be displayed using _k_friendly_name kglobalshortcutsrc. So, again, as a compromise, I'm asking that command shortcuts created with "Add New > Command or Script..." not generate a separate .desktop file. -- You are receiving this mail because: You are watching all bug changes.
