Bug 277756

+++ This bug was initially created as a clone of Bug #125102 +++

Version:           4.6.5 (using KDE 4.6.5, Gentoo)
Compiler:          gcc version 4.4.5
OS:                Linux (adm64) release 2.6.38-gentoo-r6
Locally
Move file a large file from pathA to pathB
Cancel before completion

Result
The original is left in pathA
In pathB there is an incomplete copy of foobar.

This causes problems in the following scenario.

1) Copy large number of files from flaky CDROM
2) An error causes the process to be interrupted.
3) {lastfile} is incomplete
4) Copy files again, select overwrite
5) Get stuck doing steps 1-4

6) Alternative choice, select skip existing files
7) Repeat until all files are retrieved
[Yes, I had to do that]

But there are now unknown incomplete files. 


Recommendation (for both copy/move):
copy to foobar.part
rename to foobar only upon completion
if user cancels delete foobar.part

Why this way? Even if the computer crashes the user will know that foobar.part is an incomplete file. What happens if the user looks in target directory see the incomplete foobar, assumes the process was complete, deletes original. Also, if something is referring to foobar it will not be able to reference the incomplete foobar.part.