"Move" does not "move"

[aicul]

In OS X you can drag+CMD to move a file between devices (rather than copy).

Basically this involves the transfer of the file to the new destination and delete it in the old location.

However, I have noticed in Yosemite that in some cases the "move" does not actually remove the file in the old location, and this with no warning.

Further to various tests, it is possible to replicate this simply. Open a PDF file in preview and then move the file to a new server location. Since the file is open it will not be deleted in the old location. This without warning.

I can understand why the file is not deleted in the original location, however I cannot understand the absence of a warning.

 

[Taz Mangus]

In OS X you can drag+CMD to move a file between devices (rather than copy).

Basically this involves the transfer of the file to the new destination and delete it in the old location.

However, I have noticed in Yosemite that in some cases the "move" does not actually remove the file in the old location, and this with no warning.

Further to various tests, it is possible to replicate this simply. Open a PDF file in preview and then move the file to a new server location. Since the file is open it will not be deleted in the old location. This without warning.

I can understand why the file is not deleted in the original location, however I cannot understand the absence of a warning.

I just tried your test case where I open a PDF file and while it was open I CMD-drag the same PDF file to a external hard drive. The PDF file was moved like it should. I am running 10.10.2.

I suggest that you create a new user, reboot and login to the new user. See if the issue still happens.

 

[dyt1983]

edit: To remove personally identifying information not relevant to the thread.

 

[aicul]

To me it's a non-issue because I don't expect a warning if I am not going to lose something.

It's an issue when the MOVE is to archive documents and thereafter you are left with a maze of files on 2 drives.

You are actually losing knowledge of what file is the last version of a file and have to dig into CMD-I or similar to understand what file is the true final version of a file.

Leading to mess and potential of deleting the wrong last file and time loss.

 

[dyt1983]

edit: To remove personally identifying information not relevant to the thread.

 

[aicul]

I'm sorry I wasn't clear, I said "To me it's a non-issue" and that's still true. Plus I wouldn't try to move files that are opened in Preview in the first place.

Ok, its a non issue for you ... until it is. I appreciate you personal input, but it truthfully does not help the discussion. No offense meant here ;-)

Also please don't miss-interpret an example as a unique case. The no-move issue appears in other cases to when there is no open app (as highlighted by no-dots in the docks). The Preview example is an easy example to replicate, that's why its was provided.

My thinking is; if Finder issues a warning that files exist in the destination folder, why can it not issue a warning when the very fundamental of a move (removal from original disk) cannot be achieved ?