Yes, I just want all my active macros. Here's my thought process:
Since I was under the impression that the plist contains all macros I have (enabled and disabled) and the file would change when I enable a disabled macro and vice versa, as well as updating when I delete or add a macro, that modification date would trigger a script file that would read it and make an updated list with just the active macros. I saw that the plist also contains information about my favorite actions, which is irrelevant for this case. So, if I were to use the HMTL Form, I would read from that new, shorter, cleaner, "database" (no favorite actions, no disabled macros), to make it faster to read.
Does that make sense?
And yes, for this particular case, it's for all macros, available in all apps. I have another shortcut that I use when certain apps are available with macros that are only useful for those apps. Same shortcut, different list, using the Switch action to check the front app.
The sub macro I have now is really just the right arrow keystroke. Well, at least from now on. I used to have an action to check if the window was visible, to avoid pressing the right arrow, before the window was even visible. Maybe those actions were doing more harm than good. I removed them now and I will see how it goes.
I'm not 100% sure I understand what you mean here?
Basically this would be my "ideal" view of that macro (list of the most recent macros and maybe some others, similar to when we type n:
So, basically, the n: was "embedded" in the macro itself, not visible. We wouldn't have to type anything to filter by name. This would be a toggle in the action itself or maybe even globally for all Trigger Macro by Name actions.
An action that's called "Trigger Macro by NAME" should do that without any workarounds.
I use this macro maybe hundreds of times a day. At some point, having to click an extra key does the opposite of apps like KM are supposed to do: remove unnecessary steps from our workflow.
I agree, but the point here, in my opinion, is not that we should just be "grateful" for the time the app saves us, but how things are named and how they could be implemented to make it even easier. Last case, make a "Trigger Macro by Name" that just trigger by name, and a Trigger Macro by Any Content (or something like that). I don't think this would be smart, having 2, but again, the name of the action implies "Name" not text inside the macro. If my macro is called "ABC" and I search for "XYZ", it will find it, when "XYZ" is for example inside a comment. This, to me, it's not about being grateful, it's about things not being properly named.
Sorry for the (very) long reply... 