I just spent several minutes investigating why a key didn't work in my editor, and finally tracked it down to it being a second trigger hotkey for a KM macro.
So, the question is: is there a way in KM to see all hotkey triggers? The standard views show the first one, but if there is more than one, the only way I've found to discover the nth ones it is to look at each macro individually (which is how I discovered the one in question).
Alternatively, is there something where we can type a key and KM tell us the macro tied to that trigger hotkey, if there is one?
I've done several searches on the forum and the manual and didn't find anything, but if I missed it just point me that way.
That doesn't appear to be documented; I just searched for "engine.log" in the user manual, and there is only a single reference to it in the debugging section, and then only in reference to logging details to it. Might be nice to include this information somewhere.
I looked into that first, last night, but couldn't recommend it to @v8kbm because it's really fiddly to use, I find. (Getting a command key symbol into that search box at random, sure, that's easy enough... ).
Looking at the Wiki now... I think you're right. Let's see what @peternlewis thinks.
There is perhaps the argument that if you're the sort of person that wants to look at logs, you're probably the sort of person who thinks to look for logs. But Keyboard Maestro's logs are very readable, so maybe should be promoted a little more.
I agree it would be logical for the editor to show more than one hot key if there is more than one hot key! After all, there is a %TriggerValue% token, which reflects that having more than one trigger for the same macro can be useful.
Got it. That works, thanks! And, I see after the fact that the "h:" is documented in Search Strings.
It is, however, inconsistent with the modifier keys, which can just be typed in without the h: and the search still works. Based on the earlier discussion in this thread, that's what I was trying to do with the function keys as well (I didn't read about the "h:" until just now, after I tried your suggestion.)
It's easy enough to search for hotkey triggers as has been shown.
The simplest way is to use the Keyboard Maestro Status menu to show when macros run (I use the Iconaholic Loud KM icon set for this) – and when you need to know what macro is associated switch to the Keyboard Maestro Editor and type the keyboard shortcut for the Last-Used macro.
The way to resolve this is to use the Interactive Help, in the Help menu, selecting Something unexpected is happening, and following its instructions and it will lead you straight to the macro.
You can also click and hold on the ⌘ button in the editor toolbar to select from the recently executed macros.
As noted, the search can be restricted to hot keys by preceding the entry with “h:” and modifiers can be typed by tapping them when in the search field. The “h:” restricts the match to only matching hot key triggers. You could search for the key without the “h:” and it would find the match anywhere in the macro (including the hot key trigger, but also including Type a Keystroke actions for example, or anywhere else the key might be appear).
).
But Keyboard Maestro's logs are very readable, so maybe should be promoted a little more.
