|
|
Delete matching files in two Finder folders
Another good reason why, as John Gruber suggests, replaced files should be moved to the trash, not deleted outright! Definitely a bug if it results in unintentional data loss.
Delete matching files in two Finder folders
That might be difficult to implement system-wide. If a (non-Finder) app were operating with a C API, for instance, doing an open(filename, "w") on an existing filename, you would have to capture this at the filesystem level and "Do The Right Thing" (TM), that is, move the file to the appropriate .Trash location. That doesn't exist in any existing filesystem, and you would be hard pressed to do it for legacy filesystems.
Delete matching files in two Finder folders
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.
Delete matching files in two Finder folders
I agree with your simple analysis and explanation. Here's looking at the two main perspectives in more detail: |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.21 seconds |
|