Engine log - how do I find Action number # in my list of actions?

[peternlewis]

@kevinb

Is there any logic to why the design is such that the space has to be omitted? I presume that there is (but it shouldn’t be necessary just to, say, separate search terms ).

There is always logic. Sometimes misguided, but always a reason.

The search string is broken up into "words" and each word is searched for independently. So for example if you search for One Three it will find a macro One Two Three.

You can quote things to make phrases, so for example "One Three" will not match One Two Three.

This is why you cannot write action: 1234, that is searching for action: and 1234.

But note that spaces within quotes are still treated as special in that they will match any number of spaces of any kind. So indeed it would also match an action that had One and Three on consecutive lines (or even on separated lines as long as there was nothing but empty space between them).

@kevinb

I have however just experimented by created two dummy macros, one with typed string

Ahh, well, this is a separate more technical issue. Because spaces are significant in a typed string, The Typed String trigger displays spaces in a special way, either as One◇Three or as One«Space»Three. And this is the same way you would need to search for them. I'll add the raw string in to the search for the next version.