Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Found it! (Score:5, Informative)

    by pudge (1) on 2003.11.21 18:11 (#25979) Homepage Journal
    My happening script was causing the problem, though it is a bug in that is easily reproduced with AppleScript. Here's the bug report I am filing:
    After sending an Apple event to, it ceases to open and execute .command files.
    1. Create an executable .command file on the Desktop:
      $ cd Desktop/
      $ cat > foo.command
      echo "hi"
      $ chmod a+x foo.command
    2. Quit
    3. Double-click foo.command in Finder
    4. See that opens, makes new window, and executes the script
    5. Make a new window, and execute this command:
       $ osascript -e 'tell app "Terminal" to activate'
    6. Double-click foo.command in Finder, again
    7. See that activates, but does not make new window, or execute script
    * NOTES
    FWIW, every AppleScript (actually, I discovered this sending Apple events to from Perl using Mac::Glue, but osascript is a lot easier for the sake of the bug report) I tried to use with cause the problem.  Activate, get property, whatever.
    Also, I've confirmed the script does not run, by making the .command script do something verifiable (like making a new file).  It's not merely that you don't see it running, it actually isn't running.
    So if you use happening under Panther, you may want to comment out the "extra info about Terminal" stuff.