Re: Odd Finder Behavior
Re: Odd Finder Behavior
- Subject: Re: Odd Finder Behavior
- From: Peter Waibel <email@hidden>
- Date: Wed, 6 Dec 2006 18:50:14 +0100
Has anyone suggestion how to savely delete files (data and resource
fork) on a mounted volume without using finder scripting?
You can use rm.
I do use rm on my own files
but I'm still hesitating to use rm in scripts that are used by
others.
The reason why I'm hesitating is that I do not understand what rm
really does.
That's not unreasonable, because the answer to that question
changed some in Tiger. These days, rm(1) deletes the file,
including any sort of extended meta-data it has, regardless of the
type of file system it's on. This used to not be the case -- file
systems that don't support extended meta-data such as resource
forks store the extended information as a sibling file [1], and rm
(1) would only delete the primary one.
Therefore: if you can assume Tiger, then don't worry about it, it's
all good. If not, then you probably don't have to worry about it,
because most people only use HFS+ disks, for which the problem
doesn't apply. (However, that depends some on who your customers
are.)
Great news! I didn't know that the behavior of rm is improved in Tiger.
Thanks for the detailed answer, Chris.
But there is allready the next question: Does the behavior of "mv"
and "cp" have improved as well?
Is it a good idea to use unix commands with "do script" for operating
on files
or can we expect to get improved native AppleScript commands in the
future?
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/mailman//archives/applescript-users
This email sent to email@hidden