Keyboard Maestro episode on MPU

In the most recent episode of Mac Power Users, David and Stephen discuss Keyboard Maestro, a longtime favorite automation app and the main topic of at least three previous episodes of MPU. If you’re an ANIAT reader, it’s reasonably likely that you’re already using Keyboard Maestro, and you may think this is an episode of MPU you can safely skip. I certainly considered giving it a pass, but I’m glad I didn’t. I’ll bet there’s at least one nugget in the show that you’ll be glad to have heard.

For me, it was David’s use of Keyboard Maestro’s conflict palette. I’ve known about the conflict palette for years, but I’ve always thought of it in terms of its name: a way of resolving conflicting macros that have the same trigger. To me, these conflicts are mistakes: cases in which I’ve accidentally used the same trigger on two or more different macros.

But David treats the conflicts positively. He sees the conflict palette as a useful user interface tool, a way to avoid having to come up with distinct triggers for a number of closely related macros. It’s a way of reducing the number of keyboard shortcuts you have to remember while still being able to quickly launch the macro you want.

Keyboard Maestro conflict palette example

You could, of course, build a macro that uses the Prompt For User Input action to set up a selection of other macros to run, but it’s much easier to use the conflict palette. And it’s much much easier to add new macros to the set at a later date.

I feel compelled to comment on a couple of other things that came up in the podcast:

First, there was David breaking bad on Shortcuts. David is the most tolerant Apple user I know, so when he starts talking smack, you know he’s been pushed beyond the limits anyone else would accept. As an avowed hater of Shortcuts, I loved it.

Second, Stephen has been using Keyboard Maestro in place of TextExpander. This works because typed text is one of the trigger categories that KM accepts. When David asked if there were any downsides to using Keyboard Maestro instead of TextExpander, Stephen couldn’t come up with any problems other than the initial pain of reimplementing your snippets in a new app. As someone who did exactly what Stephen did—on two separate occasions—I have thoughts:


One last note: I’ve included links above to a couple of the Keyboard Maestro Wiki pages. I don’t know what’s going on over there, but when I visited those pages they took an ungodly amount of time to load—like, 56k modem time. Maybe that’s just a temporary problem, but don’t be surprised if it seems like your browser has hung.