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 447220 - Show file size and date modified in Nautilus' overwrite warning window
Show file size and date modified in Nautilus' overwrite warning window
Status: RESOLVED DUPLICATE of bug 47893
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.18.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-13 16:59 UTC by Jorge G. Mare
Modified: 2007-08-08 01:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jorge G. Mare 2007-06-13 16:59:43 UTC
When overwriting files (with the same name), Nautilus displays a simple "The file already exists in "xxxx".  Replacing it will overwrite its contents." message.

When unsure whether it is OK to overwrite or not, the user has to cancel the operation once, check the files' sizes and dates to make sure he/she is keeping the desired version of the file, and only then restart the file copy/move operation again.

This multi-step procedure could be greatly simplified if Nautilus provided the necessary information (files size and date) in the warning window, so that the user can determine whether to overwrite or cancel (ie., OK if it is newer/bigger; not OK otherwise) without having to interrupt the original file operation.

Other information:
Just for reference, see how the Tracker file manager did it in BeOS:

http://www.myhaiku.org/haiku/2007-06-13_tracker-overwrite.png
Comment 1 Nelson Benitez 2007-06-14 08:02:22 UTC
This is a dup of bug 47893
Comment 2 Susana 2007-08-08 01:41:52 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Please follow the discussion on the other bug. Thanks.

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