#MAC MOVE INSTEAD OF COPY MAC#

In UNIX all files are set with permissions. The main problem the poster is having is getting past user permissions not a file move. I see what you are saying with this, but the more I think about it, this seems to reveal a security problem rather than a feature. This hint deserves five stars for drawing attention to the deficiency that Apple has shown no interest in rectifying since dropping 'Computer' from their name, and should get five stars for providing a functional GUI-based workaround for it. People getting hung up on the example are also missing the point.Īpple and the GUI gets one star.

The example used (post-archive and install) is just that, an example. Yes, the command line could also be used, but then why am I paying the Apple tax when I could use Linux for free? Maybe we should all be asking ourselves this question. It is a workaround that shouldn't even be necessary, but it does work.

#MAC MOVE INSTEAD OF COPY MAC#

Yeah, so Cmd-dragging in the Finder (the 'force move' action by Mac convention) doesn't do it, but using AppleScript to tell the Finder to move still works correctly. Or maybe the 'flexible engineering team' concept shunted the developer off to another project before they could get around to fixing it. It wouldn't have been off-topic five years ago, but whoever Apple brought in to work on the Finder after 10.3 probably wasn't familiar with Mac conventions and broke it. The whole Cmd-key discussion is off-topic. As pointed out earlier, the GUI doesn't allow moves across owners or where permissions otherwise don't allow it. I'm not the submitter, but it's pretty obvious most people commenting don't get it.

Mac move instead of copy