Comments on: AppleScript Shell

By: FredB

FredB — Fri, 22 Dec 2006 03:11:05 +0000

Really nice!

Not a big deal but at first I thought you were talking about ash.

By: Cameron Hayne

Cameron Hayne — Wed, 20 Dec 2006 18:29:31 +0000

I have now received two reports of problems with Ash from people with Intel Macs, so I suspect there is a PowerPC vs Intel issue.
For these people, Ash fails on all AppleScripts with an error like the following:
Can’t call method “get” on an undefined value at /usr/local/bin/ash line 1652, line 1.

The problem is something to do with the Perl module “Mac::OSA::Simple” that is used to compile and execute the AppleScript.
I now vaguely recall something about some of the Perl modules that call Carbon having byte-order problems, so it’s probably something like that in the Mac::OSA::Simple module that is causing the problem. (I don’t have an Intel Mac, so I’ve only tested Ash on PowerPC.)

A work-around is to use Ash’s command-line option “-osaMethod” to change the method used to execute the AppleScript to use the ‘/usr/bin/osascript’ tool instead of using that Perl module. To do this, start Ash with the command:

ash -osaMethod osascript

Using the ‘osascript’ method in Ash is fine and you could change this to be the default by editing the Perl script and changing the variable ‘defaultOsaMethod’ on line 86. The only issue is that Ash will be slightly less efficient since with this method, it execs /usr/bin/osascript each time you execute an AppleScript command. Most people won’t notice the small overhead this causes.

By: Daniel Jalkut

Daniel Jalkut — Wed, 20 Dec 2006 17:18:21 +0000

ssp: I’m not sure - I am almost always logged in as me, so it’s not an issue in my case. I thought I heard something about Mac OS X getting better at running “login-less” at some point (10.4?). Maybe that is what Steve is alluding to.

By: Daniel Jalkut

Daniel Jalkut — Wed, 20 Dec 2006 17:16:54 +0000

adrianm: it’s just a step up from the “all at once” execution style of osascript. With ash, you can play around with the script interactively. The example I pasted above was sort of a “staged” example in that I had already figured out how to do everything. But the interactiveness of ash is what makes it more useful for this type of thing - you can explore the results of commands and examine properties of AppleScript objects in order to figure out how to access what you want. Just like in Script Editor.

By: adrianm

adrianm — Wed, 20 Dec 2006 17:10:41 +0000

why not just use osascript -e ?
bash lets you write a multiline script before execution.

By: Steve Streza

Steve Streza — Wed, 20 Dec 2006 16:01:54 +0000

ssp, it’ll launch applications just fine, you just won’t be able to see them on the remote machine. You don’t even have to be logged in through the OS X login panel.

By: ssp

ssp — Wed, 20 Dec 2006 09:10:48 +0000

Does this require you to be logged into the machine? I’ve always wondered what happens when running an AppleScript via ssh. Can it launch GUI applications and all although you don’t have a desktop? Will it just fail? (Will it access the apps of the currently logged in user? I guess not, but you never know ;)

By: Nicholas Riley

Nicholas Riley — Wed, 20 Dec 2006 06:22:24 +0000

Or you could use contacts, a command-line client to OS X's Address Book. For scripting from the command line I prefer the Python scripting bridge appscript, which has a great contextual terminology browser (just use .help() on any object), in combination with the enhanced Python shell IPython.

By: Peter Hosey

Peter Hosey — Wed, 20 Dec 2006 02:10:00 +0000

Sounds a bit like a Terminal-based version of CLImax.