There are several ways to use AppleScript within Bunch.
* at the beginning of a line to have the line interpreted as raw AppleScript. There will be some permissions requests and some commands that just refuse to run, but try it out. You can open Console.app to see any errors that your command might run into. This feature is only marginally tested.
* say "Welcome to the communications context" * do shell script "/bin/bash my_cli_tool.sh" * display notification "Bunch Opened"
If the content of a
* line references an existing filename, that file will be executed as an applescript using the
osascript command. If the script is in your Bunch directory, you can run it with just the filename (or a relative path to a subfolder1). Otherwise, specify an absolute path to the script.
* MyScript.applescript * OtherScript.scpt
If your script has a space in the name, you need to either quote the name or escape the spaces, e.g.:
* "My Script With Spaces.scpt" * My\ Script\ With\ Spaces.scpt
Arguments can be passed to the script on the same line (same escaping rules apply):
* MyScript.scpt "argument 1" argument\ 2
Scripts run using
* commands are monitored like shell scripts, and show up under the “🔴 Shell Scripts” menu.
You can also wrap the AppleScript in an Automator Workflow and run it using
& commands. This also makes it easy to use variables and control where output goes.
Remember that relative paths in Bunches within subfolders are relative to the base Bunch Folder, not the containing subfolder. ↩