You’re also going to end up wanting to do a lot of customization.
Atom supports keymapping, but I found it confusing and it didn’t always work. So all my keymapping is done in KM.
One of my most-common used macros involves working on HTML or JXA scripts, that are going to be used in KM. For example, I’ll have a KM action that runs the script file I’m working on. So when I’m in Atom, I press F15 and it saves the script, then triggers the macro that uses the script. Works really well.
Oh. This is embarrassing. I keep meaning to make this better. Here's the macro it runs right now:
I just disable and enable the macro I want to run as needed. I keep meaning to add a "Long Press" option to pull up a pick list, but I never seem to get around to it, even though every time I go in this macro and enable/disable, I feel shame. .
I think I’d put the macro name or UUID in a comment at the top of the file, so I didn’t have to manage the target macro in the runner macro — but I won’t know for sure until I start building workflows.
Looks like AppleScript support sucks. Is there a way to get the path of the front document?
I haven’t tried, but the if you hover over the tabs, you get the full path, so I suspect you might be able to get it via UI Browser. If you figure it out, let me know.
I shamed myself into fixing this, so I’m use a modified version of my Execute Macro by Name (Spotlight) macro to allow me to pick from a list (long keypress), or run the last one selected. Should be done soon.