Bug 414799

Summary:	Incompatible shortcut preset
Product:	[Frameworks and Libraries] frameworks-kconfig	Reporter:	Matthias <shalokshalom>
Component:	general	Assignee:	Matthew Dawson <matthew>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kdelibs-bugs, nate
Priority:	NOR	Keywords:	usability
Version:	5.64.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Matthias 2019-12-03 16:20:27 UTC

SUMMARY

The secondary setting for cut and the primary one to delete files are both the same:

STEPS TO REPRODUCE
1. Look into the general shortcuts
2. Enter Shift+Del in the search


OBSERVED RESULT

Cut and Delete are both set to Shift+Del

EXPECTED RESULT

Cut has no or another secondary shortcut

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KaOS current
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2019-12-03 19:39:22 UTC

Oops. Bug in kconfig: https://cgit.kde.org/kconfig.git/tree/src/gui/kstandardshortcut.cpp#n83

Comment 2 Nate Graham 2019-12-03 20:25:46 UTC

I've submitted a patch that fixes this: https://phabricator.kde.org/D25720

Comment 3 Nate Graham 2019-12-09 16:05:01 UTC

The patch led to a lengthy discussion and we decided not to change this because we would have to choose between who to break and we don't want to break anybody. :) There's already an exception for this son in practical usage in apps, there's no problem.

Comment 4 Matthias 2019-12-10 17:35:41 UTC

You break now both?

Comment 5 Matthias 2019-12-10 17:39:17 UTC

And you are quite aware that this secondary shortcut is..  Aehm..  A secondary shortcut? 

Show me one single person who does not crtl+X to cut, this is standard since the 90ths oO
Cant believe we are talking about this since I reported it because it broke for me. Thanks a lot

Comment 6 Nate Graham 2019-12-11 09:29:26 UTC

What specifically broke for you? If you read the linked discussion, you'll see that we actually added a workaround for this so that they don't actually conflict so I would like to know which use cases are still broken so we can fix them?

Comment 7 Nate Graham 2020-01-15 19:32:29 UTC


*** This bug has been marked as a duplicate of bug 394001 ***