Bug 183057 - deleting from folder panel always moves to trash
Summary: deleting from folder panel always moves to trash
Status: RESOLVED DUPLICATE of bug 194275
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-03 22:00 UTC by Zen
Modified: 2010-09-13 17:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zen 2009-02-03 22:00:35 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

Holding down shift and choosing 'move to trash' in the folder panel always moves to trash while it should delete directly like it does from the right hand view.
Comment 1 Dotan Cohen 2009-05-27 09:05:15 UTC
I can reproduce this issue on Kubuntu 9.04 with KDE 4.2.3. It is unexpected behaviour.

See also this related bug:
http://bugs.kde.org/show_bug.cgi?id=194275
Comment 2 Dario Andres 2009-10-23 01:28:26 UTC
Mh, in fact, as Dotan mentioned in his bug report, it is an unexpected behavior. I would not expect "Move to Trash" to magically convert itself into "Delete" without notifying the user properly. That is why you can configure Dolphin to show both entries("Delete" and "Move to Trash" in the contextual menu)
Regards
Comment 3 Zen 2009-11-10 10:37:03 UTC
Dario, Dotan said it was unexpected behavior that shift+trash does not delete. Also this works and never has been a problem in the file view, it just doesn't make sense to have different program behavior in every panel. Besides, having the delete option in the context menu makes for easier accidental (permanent) deleting than having to hold a modifier key down.
Comment 4 Mark 2010-09-13 17:28:46 UTC
Marking as duplicate of 194275 since that bug has more information about the actual issue.

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