This appears to be the case:
A macro with the following form:
<command name="test">
<macro>
<choice>
<sequence>
<match [context+pattern]/>
[actions]
</sequence>
</choice>
</macro>
</command>
works as expected if called directly ([actions] are performed if match
[context+pattern] returns true). If this macro is called from another macro,
however, and match [context+pattern] does not return true, then all actions
are abandoned, including any remaining actions in the calling macro.
If I add a second <sequence> element containing a dummy action that can
always be executed, then the macro works as expected.
Kevin Flynn
Birdstep Technology ASA
Oslo, Norway
