Re: Old AppleScript applications stopped working
Re: Old AppleScript applications stopped working
- Subject: Re: Old AppleScript applications stopped working
- From: Doug McNutt <email@hidden>
- Date: Sun, 26 Aug 2007 13:22:46 -0600
At 10:22 -0700 8/25/07, Ed Stockly wrote:
>May not be a problem with the scripts. You may want to run disk utility, fix permissions, even reinstall your system.
At 10:53 -0700 8/25/07, Philip Aker wrote:
>AppleScript applets and droplets get most of their abilities by loading code from the System at startup. They are not true applications either in the Classic Mac OS or OS X sense.
Problem solved! Between the two of you I found some interesting things. Thanks for the replies.
What happened is that the UNIX execute bit on some AppleScript .apps got cleared. It happened when I was messing around with chmod with the -T option. I was trying to clear out execute bits that made no sense for files that were not directories or true executables. I assumed - silly me - that all Aqua applications were really directories posing as packages and that the -T option would reset the execute bits appropriately. It's not so for Applescript apps.
Apparently those AppleScript apps are true, single file, executables in the UNIX sense. The command lines:
cd $HOME/bin
./CleanUp.app
execute a Compiled script just fine. FE ED FA CE are the first 32 bits of the AppleScript app and I'm fairly sure that they stay the same. Is that some kind of #! line that applies to Finder? Does Finder recognize it and fork the "app" as though it were a simple executable in BSD UNIX? Why does Finder insist on the execute bit? It totally ignores those bits in the file info window.
And more to the point. . . Can I add the phunny shebang sequence to the result of a compiled block of code and thereby persuade Finder to execute it on a double click? An automatic "do shell script"?
Does Finder recognize all 32 bits of that header? It's followed by three nulls and a hex 12. Can I somehow fake out Finder so that my #! shell scripts can become double-clickable? Most of my AppleScript applications do nothing more than pass control to shell. AppleScripts are easier than burying a script into a package directory with a /Content/ and other required junque.
I shall take Singh's book to bed with me tonight. Perhaps Finder can grow up to be a real shell instead of a wooden doll.
--
--> From the U S of A, the only socialist country that refuses to admit it. <--
_______________________________________________
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/archives/applescript-users
This email sent to email@hidden