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 626742 - Replacement dialog when you cut a file and paste it in the same directory
Replacement dialog when you cut a file and paste it in the same directory
Status: RESOLVED DUPLICATE of bug 764842
Product: nautilus
Classification: Core
Component: Cut Copy Paste Undo
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-12 15:13 UTC by Pedro Villavicencio
Modified: 2017-08-28 22:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description Pedro Villavicencio 2010-08-12 15:13:11 UTC 
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/615698

"Steps to reproduce:

1. Cut some files in a directory
2. Paste those in the same directory

What happens:

You get a file replace dialog window

What should happen:

No dialog should pop-up if there's nothing to replace."
Comment 1 Fabio Durán Verdugo 2010-08-12 15:16:08 UTC 
Yes I can confirm this bug.
Change the status to NEW
Comment 2 António Fernandes 2017-08-20 21:46:53 UTC 
Still valid in 3.25.90. The same thing happens with the "Move to…" dialog.

Nobody wants to move a file to the where it already is, by definition. However, the "cut" metaphor gives the idea that the file was picked up from where it was, so it follows that users may "paste" it back in the same place if they want to cancel the operation.

Therefore, my suggestion is: pasting in the same directory should cancel cut (making the file opaque again and dropping it from the clipboard). In the "Move to…" dialog there is already a [Cancel] button, and the [Move here] button should be made insensitive while in the source directory.
Comment 3 António Fernandes 2017-08-28 22:01:52 UTC 
A fix for this is already discussed in another report, so let's close this report and track the bug there.

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