Why Does Clicking on Applescript Notifications Open the AppleScript Editor?

First, the display notification command has nothing to do with Growl: it's a part of the Standard Additions osax that uses the user notification center that's built into Mavericks. I have no idea what changes Growl has undergone since the user notification center was incorporated, but I imagine they are significant, and that many of your scripts will need to be rewritten from scratch.

As for the main question, the Script Editor is the default application for applescripts, so when you launch a notification from an applescript it will assume that the action of the notification points back to the Script Editor. This will be true even if you launch the notification from osascript (since the system will still consider it a script). I don't know of any way around this - encasing the command in a tell block doesn't help, at any rate.

HalNineThousand wrote:

So, as I understand it, any AppleScript use of a normal notification will mean, when I click on it, that it will want to go to the Script Editor (unless I can find a way to go to some other application - in which case, it'll still open some application or switch to the Finder when I dismiss the notification).

If I add Growl, can I create notifications in AppleScript that use Growl that don't automatically open an application?

In vanilla applescript, that is the case. Applescript's notifications support is sparse. If you want to switch to applescript-objc you can get more control over notifications, including choosing the action that occurs when a notification is clicked. ASOC requires snow leopard or later (or Mavericks if you want to create a script library for more versatility). I can pound out an asoc script later if that's out of your skill-set (or someone else may do it; on my way to a meeting right now).

I haven't looked at Growl in a few years, so anything I might say about it is out of date. You should check their webpage.

I haven't tried this but there is some interesting info here ◆ System Notifications Support

How aout that this works

displ

display notification 'A notification."

I wonder if 'Terminal notifier' helps with any bash/ python scripts…

https://github.com/alloy/terminal-notifier

The manual has these two nuggets…

-open URL The URL of a resource to open when the user clicks the notification.

-execute COMMAND A shell command to perform when the user clicks the notification.

Could be worth a look.

I have used it with scheduled bash scripts.