does - g mine which is an alias 'then' executes the previous commands. Why? I expect them to be executed in the order given, not based on the precidence of aliases vs. normal command input (which should only effect the one command). There shouldn't be a functional difference between command stacking and entering them as seperate commands.
Sigh.. Beginning to hate my power company. This is the 4th. time I will have tried to type this due to 'typical' summer power outages. lol
In any case, having looked more carefully at what is happening it looks like the priority problem is not in the aliases, but in the world.sends being used in the script that gets called. This still makes no sense logically, but what is happening is you send the following stacked commands using ;>
command/alias
command/alias
alias - calls script
and the result is actually:
world.sends from the called script
1st. command/alias
2nd. command/alias
This is definitely not expected behavior from the users perpsective imo, since the expectation is that a scripts commands will act just like a normal one and execute in the order given in the stacked commands. Instead it does the script first. :p
Don't remember reading that one, but thanks. Nice to know it is known. Though.. actually looking at the post, it is the same problem, but 'slightly' different conditions. Or at least I assume that ctrl-enter works a little different than employing command seperators. Hard to tell without knowing the internal workings. ;)