ASH lets you do the following:
batch_open();
take_closet( item1 );
take_closet( item2);
batch_close();
at which point, a single command is submitted to the CLI:
closet take item1, item2
batching works for many ASH functions that are implemented in terms of CLI commands. In particular, it will batch commands of the general form:
<command> <prefix> <rest>
While you are batching, multiple functions that go to the same <command> are saved up until you do batch_close. The catch is, it currently only saves up a single <prefix>; you can batch multiple "closet take" commands, but if you mix in a "closet put", it is executed immediately.
It doesn't have to be that way. It should allow multiple commands (as now) and also multiple prefixes within each command, so that when you do batch_close(), all your "closet take" will be grouped together AND all your "closet put" will be grouped together.
batch_open();
take_closet( item1 );
take_closet( item2);
batch_close();
at which point, a single command is submitted to the CLI:
closet take item1, item2
batching works for many ASH functions that are implemented in terms of CLI commands. In particular, it will batch commands of the general form:
<command> <prefix> <rest>
While you are batching, multiple functions that go to the same <command> are saved up until you do batch_close. The catch is, it currently only saves up a single <prefix>; you can batch multiple "closet take" commands, but if you mix in a "closet put", it is executed immediately.
It doesn't have to be that way. It should allow multiple commands (as now) and also multiple prefixes within each command, so that when you do batch_close(), all your "closet take" will be grouped together AND all your "closet put" will be grouped together.