I understand.
My approach is as follows.
If you use many scripts, using a shortcut for each using System Preferences gets to be a pain in the neck, and you need an elephant’s memory to remember them all. With KBM, you can use as many shortcuts as you want. Each shortcut triggers either a single script or displays a palette (=menu) of scripts on the screen from which you can choose one or multiple scripts to run (you can configure the palette so it disappears every time you run one action or stay displayed until you press a key like escape which allows you to run multiple scripts in sequence.
If you want to try the keyboard maestro route:
- in DevonThink→ open scripts folder → go to the script you want to run → context menu → copy UNIX path of the script of interest
- in keyboard maestro → new macro → assign a trigger (keyboard shortcut) → insert execute AppleScript action → run as FILE (not text) → paste the UNIX path , and your macro/script is ready to run.
If you have multiple macros for multiple scripts, you have 2 options:
- one shortcut per macro/script
- even better and easy to remember: give all (or part of) the script macros the trigger (keyboard shortcut). When you type that keyboard shortcut, all macros triggered by that shortcut will be displayed in a nice menu (palette, in this case called a “conflict palette” because multiple macros are the same trigger). Conflict palettes are one of the most useful and commonly used features of keyboard maestro