GNOME Bugzilla – Bug 95585
Copying/moving a folder replaces a similarly named folder in the destination
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.1.0 Synopsis: Copying/moving a folder replaces a similarly named folder in the destination Bugzilla-Product: nautilus Bugzilla-Component: File and Folder Operations Description: Description of Problem: Copying/moving a folder to a location that has a folder of the same name replaces the old folder, instead of adding the contents of the newly copied/moved folder to it. Steps to reproduce the problem: 1. Create folder "pants" in one location, create a folder "pants" in another location and touch a few files in it. 2. Copy the "pants" folder with files in it to the same location the empty "pants" folder is in. Actual Results: Nautilus will pop up a dialogue asking if you want to replace the "file" (not folder, as it happens, so this is probably just not special cased) "pants". You can choose "Replace" (which deletes the old "pants" folder and puts the copied/moved one in its place) or "Skip" (which skips the entire operation). Expected Results: One of two things: 1) The contents of the copied/moved folder should be copied/moved into the folder with the same name in the destination, and the source folder should be deleted. 2) A dialogue should pop up with "Folder blah exists, do you wish to replace it, or add to it?" (or something sensible) with the buttons "Replace" and "Add" (needs a better word) I think solution 1 is perfectly valid (Windows Explorer does this), and avoids the silly confusing semantics issues in point 2. It's also non-interactive, so the right thing will happen by default, without user interaction. How often does this happen? Regularly, I find it annoying because I do this a lot. :-) Additional Information: Nautilus is kicking so much arse! ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-12 00:32 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
You had me with you until you said "...and the source folder should be deleted" in option 1 of the expected results. How is your option one different from the current results? Also, if someone does option 2 (what I recommend as well), there should be a cancel button as well, and the default should probably be add. Well, the default is more debatable.
The source folder should be deleted if you're moving. I absolutely do NOT recommend option 2. I just put it in there for completeness. I was hoping to illustrate a point (that it was total crack). :-)
this is a windows vs. mac functionality issue, we currently use mac style, there is more discussing in bug 48085. *** This bug has been marked as a duplicate of 48085 ***