Now, see, if I set up an alias that does 'WHO' when I type 'test', and I do a command stack which does two commands and then 'test'... it does do the first two commands, and then the WHO. But if the alias calls a script which does the same thing, it does the WHO first.
Which does, in fact, look like it's a bug in the client. The command stacks ought to do each command individually, and not evaluate the script for an alias until it's already handled the items ahead of that alias in the command stack. If it won't process a *normal* alias until the right point, it also shouldn't do a script until that point.
What happens if you've got a very large stack, like A;B;C;D;E;F;G;H;I, and the alias there is actually C, but all the rest are regular commands? If the script doesn't delay, it'll be sent too soon... but if it delays, it'll go too late. The script needs to be processed at the point where the command is. |