Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Delete matching files in two Finder folders' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Delete matching files in two Finder folders
Authored by: jacobolus on Sep 14, '05 11:19:32AM

Except that we're talking here about the Finder, not third party apps that are opening files for writing. I'm not suggesting that a unix mv, or a call to write to a file move a file it's replacing to the trash, merely that the Finder do so. Then we could avoid problems such as this one of having the Undo command not actually undo all changes, in the process possibly losing important data.

[ Reply to This | # ]
Delete matching files in two Finder folders
Authored by: sjk on Oct 09, '05 04:43:14PM

I agree with your simple analysis and explanation. Here's looking at the two main perspectives in more detail:

From Finder, crippling Undo context by not restoring files that were replaced by the copy or move is quite arguably a bug because it redefines Undo's anticipated (and intuitively intended, especially for novices) meaning and behavior. However, that does have issues like mmacho mentioned. Anyway, at least for me, Undo usually means "restore everything affected by an action to the state it was in before that action".

From a shell, traditional versions of commands like cp and mv are defined and designed to be irreversibly destructive. There are non-destructive replacements available but unless underlying syscalls are modified (e.g. like SeanAhern's shim) there are too many ways to circumvent non-destructive behavior.

And that leaves us with a mix of what's expected, what's possible, and what actually happens. :-)

[ Reply to This | # ]