Re: Scripting Image Events - some kind of bug ?
Re: Scripting Image Events - some kind of bug ?
- Subject: Re: Scripting Image Events - some kind of bug ?
- From: Dave Lyons <email@hidden>
- Date: Wed, 14 Sep 2005 20:24:46 -0700
Finder creates new folders with the default permissions (and I
suspect the same is true, for example, if you create a new folder
from inside a Carbon or Cocoa "save" dialog). I see that various
standard subfolders of Home are created with no access for anyone but
the owner (700, rwx------), but this is not the same as saying that
all folders should be created that way.
If you want to control the permissions on new folders, system-wide, I
believe there is a supported way (in Tiger) to configure the "umask"
value (I can dig it up if needed).
Cheers,
--Dave
On Sep 14, 2005, at 5:22 PM, Matt Neuburg wrote:
On or about 9/14/05 2:36 PM, thus spake "Dave Lyons"
<email@hidden>:
On Sep 14, 2005, at 11:36 AM, Matt Neuburg wrote:
Of course, the Finder's own ability to apply the correct
permissions when creating a folder is no better. To see an
example, make a folder at the top level of your home directory.
The permissions will be wrong. m.
OK, I'll bite (since I work on the Finder). I tried File > New
Folder, 'tell application "Finder" to make new folder at home',
and Terminal "mkdir untitled-folder". In all three cases, the
permissions on the new folders were 755 (rwxr-xr-x) and were owned
by my logged-in user. Is something wrong with this
Sure. Compare Documents, Library, etc. m.
_______________________________________________
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