Keyboard Maestro is essentially an IDE for automation. You create macros of actions that you can then easily call from Karabiner.
It has a wonderful community that is happy to help with whatever you are trying to achieve.
I share all the macros I use with the app.
- It is always better to run compiled AppleScripts.
- Assert action. "If not condition, then fail". Useful for checking if you got right kind of data.
- You need to set ENV_PATH variable to make sure all your shell tools work in KM.
- You can read the full text of any error message in the Engine.log file (Help ➤ Open Logs Folder), and make sure (at least when testing or having problems) that the Execute Shell Script is configured to display the result in a window so you can see any error message.
- Keyboard Maestro converts any variables that start with ENV_ into environment variables when it launches sub-processes.
defaults write com.stairways.keyboardmaestro.editor MouseGetCountdown -int 3will change the timer for getting coordinates from 5 secs to 3.
- Can dismiss palettes with
- Useful to sort macros by
Date modified. Applies to most other tools too like Finder.
- The trick is to work incrementally. Find out how to successfully evaluate and display something atomic. And then gradually elaborate, layer upon layer.
System Clipboard variable
Var as token
Var for shell
- How I manage my huge KM library
- KM forum - Great place to discuss all things related to KM.
- Best Macro List
- Automating KM editor
- 6 months in, what I wish I knew on day 1 with KM
- Exporting KM Macros with KM Macro
- Little Approach I use to quickly prototype new macros
- Simplicity vs Complexity
- KM Wiki (Quick Start)
- Keyboard Maestro Course
- From TextExpander to Keyboard Maestro… again (2021)
- Archiving and version control for Keyboard Maestro (2021)
- Design Maestro - Automate your design workflow.
- Alfred - Conductor for Keyboard Maestro
- How to use conflict palettes in Keyboard Maestro (2022)