After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 740592 - Move or copy overwriting files
Move or copy overwriting files
Status: RESOLVED DUPLICATE of bug 339420
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.10.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-11-23 19:22 UTC by Danilo Silva
Modified: 2018-06-14 23:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Danilo Silva 2014-11-23 19:22:24 UTC
This is a feature request.

I have to copy/move files from one folder to another and when I have to do so I copy the files, paste on the destination folder and get away from the computer. Usually that is because the process will consume a lot of time.
After a while, I come back to the computer just to discover my operation barely began because the system is asking if I want to overwrite a file. That is so frustrating.
Could Nautilus provide a smarter way of copying files?
For example: the remaining files being copied and holding the duplicates to ask the user what to do?

Thank you.
Comment 1 jarlathreidy 2014-11-23 19:36:11 UTC
I can confirm this issue.  It would be ideal if the files that do not require user intervention continued processing while waiting for user input for the remainder.
Comment 2 Michael Ireland 2014-12-12 11:53:18 UTC
I also confirm this issue.

I think the simplest solution is as Jarlath points out - simply continue processing the remaining files, and request user input for the conflicting files after all non-conflicting files were complete.  This would apply to directory merging, existing filenames, or other conflicts.
Comment 3 António Fernandes 2018-06-14 23:22:51 UTC

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