Hi, 1. I've selected a bunch of files within a thunar's tab (the right tab) 2. Then I've opened a terminal within the directory (of the selected files) on the (left) tree-view tab via the right-click 3. And changed the permissions (it was R/O) to the directory: chmod u+w . There was some flushing within the thunar's tab, however ONLY the files I wanted have been still selected, so it has seemed there's the focus on the tab with the selected files --- and there I see the problem just here --- 4. I've pressed the Del key and and clicked on the OK button (overlooking that there actually was the NAME OF THE DIRECTORY from the left panel mentioned, although it seemed NOT to have a focus) 5. So ALL files have been deleted, as it tried to delete the (whole) directory I'd say this is a pretty unexpected result as a user can see files still selected within the right tab. === system info === $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial $ thunar --version Thunar 1.6.11 (Xfce 4.12) Copyright (c) 2004-2015 The Thunar development team. All rights reserved. Written by Benedikt Meurer <benny@xfce.org>. Please report bugs to <http://bugzilla.xfce.org/>
Thanks for reporting ! I can reproduce the problem, and I agree that it should be fixed. There are different possibilities how it could be fixed with different advantages / disadvantages. 1. Dont listen to shortcuts when tree-view is selected --> some tree-view-users will miss the feature 2. Always apply shortcuts to the right side, not to the tree view --> Possibly as well unexpected for some tree-view users 3. Unselect stuff on the right side when selecting parent folder on the left. (any disadvantages?) 4. Use a different color for "highlight current folder" on the left, so that it is clear when the gets selected. 5. ? I would pick 3, ideally together with 4. However 4 probably will be alot of work to implement.
*** Bug 15030 has been marked as a duplicate of this bug. ***
Possibly this bug is a duplicate of Bug #14369
*** Bug 12638 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 14369 ***