https://bugs.kde.org/show_bug.cgi?id=362542
John <ilikef...@waterisgone.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ilikef...@waterisgone.com
--- Comment #10 from John <ilikef...@waterisgone.com> ---
Why is this fixed only for the copy operation?
Shouldn't be fixed also for the move operation?
Which is actually even more dangerous than the copy operation!
As with a broken copy you can just delete all the already copied folders and
files in the destination ans start over the copy.
But with an interrupted move operation, it's hard to know what has already been
moved and what happens when you try to move again the remaining items.
Another thing, can't this also be extended to inhibit the suspend for the
archive / unarchive operations too?
--
You are receiving this mail because:
You are watching all bug changes.
