https://bugs.kde.org/show_bug.cgi?id=500967
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #1 from Nate Graham <n...@kde.org> ---
If something has default shortcuts, those can be disabled rather than removed,
yes. Non-default shortcuts can only be removed though. And for custom commands,
since they by definition have no default shortcuts, they therefore inherit the
"can only be deleted, not disabled" behavior. So I can see where the issue
comes from with your use case.
The thing is, if we did add the functionality you're requesting, surely the
"this is a pain in the ass" behavior would simply shift to the annoyance of
having to disable and re-enable the shortcut. It wouldn't actually stop being a
pain in the ass, right?
In general, since the shortcuts are global in scope, you want to avoid overlaps
with apps' functionality. Generally that's accomplished by using modifier keys.
In this case, maybe Meta+F10 would be a better shortcut? Is there a reason why
that doesn't work for your use case?
--
You are receiving this mail because:
You are watching all bug changes.
