Followup:
very, very interesting:
Thirteen command timer, based on qwerty's ticks addition:
alias ttest {
.timera1 1 1 echo -a $!ticks ONE
.timera2 1 2 echo -a $!ticks TWO
.timera3 1 3 echo -a $!ticks THREE
.timera4 1 4 echo -a $!ticks FOUR
.timera5 1 5 echo -a $!ticks FIVE
.timera6 1 6 echo -a $!ticks SIX
.timera7 1 7 echo -a $!ticks SEVEN
.timera8 1 8 echo -a $!ticks EIGHT
.timera9 1 4 echo -a $!ticks NINE
.timera10 1 5 echo -a $!ticks TEN
.timera11 1 6 echo -a $!ticks ELEVEN
.timera12 1 7 echo -a $!ticks TWELVE
.timera13 1 8 echo -a $!ticks THIRTEEN
}
Check out these results:
5146648 ONE
5147648 TWO
5148648 THREE
514
9648 FOUR
514
9648 FIVE
514[color:red]9648 NINE[/color]
514[color:red]9648 TEN[/color]
515
0648 SIX
515
0648 ELEVEN
515
1648 SEVEN
515[color:red]1648 TWELVE[/color]
515
2648 EIGHT
515
2648 THIRTEEN
The purple lines are completely misplaced commands to begin with. How 9,10 got in front of 6, i do not know. Also note how many skips are observed. The amount of error seems to increase as more timers are put into the list. In fact, 13 timers have atleast one skip or misplaced command about every time I've tested this alias
Another test:
5584680 ONE
5585680 TWO
5586680 THREE
5587680 FOUR
5587680 NINE
5588680 FIVE
5588680 TEN
5589680 SIX
5589680 ELEVEN
5590680 SEVEN
5590680 TWELVE
5591680 EIGHT
5591680 THIRTEEN
And another:
5690680 ONE
5691680 TWO
5692680 THREE
5693680 FOUR
5693680 FIVE
5693680 NINE
5693680 TEN
5694680 SIX
5694680 ELEVEN
5695680 SEVEN
5695680 TWELVE
5696680 EIGHT
5696680 THIRTEEN
Notice that 9 always seems to come at around the 4th or 5th timer. In fact, the entire result seems to have some sort of pattern-- the last result was exactly equal to my first. Weird
I have no idea what to make of this, besides the fact that I'm now
positive there is a bug, and I'm pretty sure it's related to multiple timers executed in one script process.
qwerty: can you come up with a way to test 2 seperate script processes executing multiple timers? They have to be executed at the *same time*.. I just want to see if it's related to being run from one process