+1 it doesn't seem to me that shift+delete is used elsewhere.

Shift + Delete for cut is the old timer Unix cut shortcut, you're going to piss lots of people off if you remove that shortcut from every single application just because it causes a conflict in applications that do file management

It's not just old timers, it's an accessibility thing for people who are left handed.

Ack. So shall we change the shortcut for delete file then? Any suggestions?

Shift+Delete is a widely known shortcut combination for "Delete File Immediately, do not send to the Recycle Bin"

We have to change something, or else there's conflict that breaks both of them in apps where both actions are implemented. Changing anything breaks someone's workflow; the question is whose we can live with breaking.

What are the applications where both actions are used and thus one may notice this conflict?

For example Dolphin

Though Dolphin seems to have some kind of local hack to make Shift+delete work for file deletion. But it doesn't work for Cut. It's all pretty messy.

In D25720#572291, @ngraham wrote:

Though Dolphin seems to have some kind of local hack to make Shift+delete work for file deletion. But it doesn't work for Cut. It's all pretty messy.

I don't know the internals of Dolphin, but it works. And I still don't get why we need to change anything in KConfig.

Apps that need both should be aware of it and remove the secondary Cut shortcut.

Or if you want to be mega fancy you can make kactioncollection (or something in xmlgui) do that

In D25720#572326, @aacid wrote:

Apps that need both should be aware of it and remove the secondary Cut shortcut.

Or if you want to be mega fancy you can make kactioncollection (or something in xmlgui) do that

I don't think we should make apps work around problems in a framework. You can also see the issue in System Setting itself. Trying to assign anything to Shift+Delete shows the "conflicting shortcuts" error dialog.

Trying to assign anything to Shift+Delete shows the "conflicting shortcuts" error dialog.

But that's fine, no?

I mean this is the user assigning a shortcut that already exists, not any different than the user trying to assign Ctrl+C somewhere. If he doesn't like the conflict, she can go to the other one and remove it, no?

In D25720#572291, @ngraham wrote:

Though Dolphin seems to have some kind of local hack to make Shift+delete work for file deletion. But it doesn't work for Cut. It's all pretty messy.

Yes it's messy but it's Microsoft fault since they chose to use an already used shortcut for another thing and we are doomed.

Some years ago I submitted the very same patch and it eventually led to 8eabbf6725386e716b7536c71a9181dfe5d959f0 in kxmlgui, which automatically handles the conflict for those few apps that need both actions (dolphin, gwenview, etc.)

(Too bad reviewboard was shutdown, I had to dig in my mail to find it :/)

So imho #414799 should be closed as intentional.

In D25720#573926, @elvisangelaccio wrote:

In D25720#572291, @ngraham wrote:

Though Dolphin seems to have some kind of local hack to make Shift+delete work for file deletion. But it doesn't work for Cut. It's all pretty messy.

Yes it's messy but it's Microsoft fault since they chose to use an already used shortcut for another thing and we are doomed.

Some years ago I submitted the very same patch and it eventually led to 8eabbf6725386e716b7536c71a9181dfe5d959f0 in kxmlgui, which automatically handles the conflict for those few apps that need both actions (dolphin, gwenview, etc.)

(Too bad reviewboard was shutdown, I had to dig in my mail to find it :/)

So imho #414799 should be closed as intentional.

May I suggest adding a comment in the code here mentioning 8eabbf6725386e716b7536c71a9181dfe5d959f0 for future reference? :)

Good idea, done in 912ec731b8bd9eca12ae21920c81bcddfb46622b.