GNOME Bugzilla – Bug 361280
copy paste folder with the same name can't add files
Last modified: 2013-04-22 14:11:04 UTC
I have created a directory structure like this one: ./destination ./destination/the-same-name ./destination/the-same-name/0 ./destination/the-same-name/1 ./destination/the-same-name/2 ./destination/the-same-name/3 ./destination/the-same-name/4 ./destination/the-same-name/5 ./destination/the-same-name/6 ./destination/the-same-name/7 ./destination/the-same-name/8 ./destination/the-same-name/9 ./the-same-name ./the-same-name/0 ./the-same-name/1 ./the-same-name/4 ./the-same-name/6 ./the-same-name/8 ./the-same-name/9 ./the-same-name/10 then in nautilus I cut ./the-same-name and paste it into ./destination. Here a dialog pop's up: The folder already exists, replace would erase any conflicting file You can ignore, and it won't move ./the-same-name/10 , you can replace, It will move all file in ./the-same-name. There probably should be an option "add new files" that will not move all files, but just move ./the-same-name/10 and remove all files. This probably should be done with care because source file will be removed. The same happen if you copy/paste the files, it's clearly safe to have an option "add new files" if you copy at least. Other information:
This bug is from a ubuntu bug: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/4294
Currently, nautilus will offer to merge the folders instead of replacing. While merging, a dialog asks what to do about each conflicting file. Here is the current dialog: > > Merge folder "the-same-name"? > > A newer folder with the same name already exists in "destination". > Merging will ask for confirmation before replacing any files in the folder > that conflict with the files being copied. > > +---+ ORIGINAL FILE > | | Size: 10 items > +---+ Last modified: - > > +---+ REPLACE WITH > | | Size: 7 items > +---+ Last modified: - > > > Select a new name for the destination > > [ ] Apply this action to all files > > [ Cancel ][ Skip ][ Merge ] > Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.