Control or launch other apps, run commands and scripts using keyboard shortcuts or from the menu bar.

How to Use ActionShortcuts

• Click icon in the menu bar and select ”Open Scripts Folder”.
• Copy your script files to the Scripts Folder or create sym links (see down below). You can create them using Script Editor and Automator apps (included in macOS) or download Sample Scripts.
  
  Supported file types are AppleScript, Automator workflows, applications, command and shell scripts (with proper shebangs).
• To set up keyboard shortcuts click icon in the menu bar and select ”Preferences”.
• To execute a command, select it in the menu or use a keyboard shortcut you’ve set.
• Hold “Option” key and select a menu item to edit the script. Or hold “Shift” key to Reveal in Finder. These actions are also available in a context menu of ”Preferences” window > “Actions” tab.

Keyboard shortcuts will only work while the app is running, but you can have the app start automatically at login using “Preferences” menu > “About” tab.

You can hide the menu bar icon or hide individual actions in the menu.

To add separators to the script list menu: use -- (double dash) anywhere in the script file name.

• Use Symbolic Links to launch scripts from other locations. Symlinks should have proper file extensions and be created using Terminal (aliases created using Finder won’t work).
  For example: ln -s SourceScript.sh ~/Library/Application\ Scripts/com.pointum.actions/TargetSymLink.sh
• Download Sample Scripts that turn on Dark Mode, hide Dock, auto hide menu bar, show the desktop and control HazeOver app.

Troubleshooting Your Scripts

• System Events got an error: osascript is not allowed to send keystrokes. (1002)

Some scripts that control keyboard input or other aspects of the system require Accessibility permission. Open “System Preferences” and navigate to Security & Privacy > Privacy > Accessibility. Add ActionShortcuts to the list of the apps that can control your computer on your behalf.

• Error: “Script file uses an unknown interpreter”

Command line scripts should have a “shebang” as the first line to tell the system which shell to run a standalone script with. See the following answer for details ↓

• Error: “command not found” or “No such file or directory” when running a shell script

The script works fine from Terminal, but gives you an error when used with ActionShortcuts? This is likely because it’s running from a non-interactive shell. In this case your custom paths and aliases are not read from your shell profile. Use the following shebang as the first line of your script to use interactive shell.

For zsh:

    #!/usr/bin/env zsh −i

For bash:

    #!/usr/bin/env bash --login

• Need help with the scripts or coming up with actions? Contact me.