Re: Script Menu In OS X
Re: Script Menu In OS X
- Subject: Re: Script Menu In OS X
- From: Christopher Nebel <email@hidden>
- Date: Tue, 30 Oct 2001 16:54:05 -0800
On Tuesday, October 30, 2001, at 08:28 AM, John W Baxter wrote:
At 2:47 -0500 10/30/2001, Chris Nebel wrote:
It's a little weird about it, though -- if it doesn't see
"#!/usr/bin/perl", it executes it using /bin/sh, which means you can't
throw an arbitrary script at it. E.g., you couldn't use a csh script
by
leading off with "#!/bin/csh". This might be construed as a feature,
but I'd consider it an iffy one at best.
Takes a powrful lot of construin' to call that a fitcher. ;-)
True, but you never know. I asked around, and it wasn't considered a
feature, merely a hack to get something usable in time for Seybold. The
author has agreed to revisit the issue soonish.
Selecting this one makes no sound.
#!/usr/bin/python
print """\aThis is a test"""
Your problem there is probably something else, since that's a valid sh
script as well. There's an architectural design point that makes it
difficult to write a script that beeps as its final action. The
difficulty is that sound output is owned by the process itself, so if it
plays an asynchronous sound (which "beep" always does) and immediately
terminates, the process, and therefore any sound output it called for,
is destroyed before you ever hear anything. You can see the same thing
with osascript:
osascript -e "beep" # the sound of silence...
osascript -e "beep" -e "delay 1" # now it beeps!
--Chris Nebel
AppleScript Engineering