Re: Renaming a copied file with Finder
Re: Renaming a copied file with Finder
- Subject: Re: Renaming a copied file with Finder
- From: Malcolm Fitzgerald <email@hidden>
- Date: Tue, 10 Oct 2006 07:58:27 +1000
On Oct 9, 2006, at 9:27 AM, Christopher Nebel wrote:
It's irrelevant, because that block will never be executed. The
Finder's "duplicate" command (without replacing) will rename the new
file as necessary ("foo copy n") to avoid a collision. ("How do I
get a reference to the new file if I don't know its name?", you ask?
"Duplicate" returns a reference to the new file as its result.)
On Oct 9, 2006, at 9:59 AM, Michelle Steiner wrote:
Copying within the same folder, yes. But my experience is if the
copy is to a different folder, it creates an error instead.
On 10/10/2006, at 4:01 AM, Christopher Nebel wrote:
My apologies; you are correct. I had forgotten that the behaviors
were different.
Sometime ago, on this topic, you advised us that this was the behaviour
we had to expect. Your suggestion then was to file a feature request,
and in the mean time to do this:
duplicate x
move x
malcolm
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden