When I run the fizmo-console command as packaged in Debian/Ubuntu, the status bar messages appear after the > prompts, separated by a row of spaces.
I'm not sure if this is just a naïve stripping of control codes from the curses version, but it does present unusual challenges for automation. For example, we can't just time out on select() of the program's stdout and make sure it ends in \n> to be sure it's ready for input.
This is fine and easy to prepare for in advance, but a little documentation of exactly what we should be watching for would be helpful. I'd also appreciate an option to have status bar text sent somewhere else, such as stderr, where it could be handled separately.
Just as an example, here's the tail end of a hex dump (eliding repeated lines of spaces) of the output of fizmo-console Tell.z5 from the Inform 6 IBG sample games, where I just started it up and then typed quit\nyes\n:
00000500 53 74 61 79 20 63 6c 6f 73 65 20 74 6f 20 6d 65 |Stay close to me|
00000510 2c 20 73 6f 6e 2c 22 20 79 6f 75 20 73 61 79 2c |, son," you say,|
00000520 20 22 6f 72 20 79 6f 75 27 6c 6c 20 67 65 74 20 | "or you'll get |
00000530 6c 6f 73 74 20 61 6d 6f 6e 67 20 61 6c 6c 20 74 |lost among all t|
00000540 68 65 73 65 20 70 65 6f 70 6c 65 2e 22 0a 0a 3e |hese people."..>|
00000550 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
*
000005a0 41 20 73 74 72 65 65 74 20 69 6e 20 41 6c 74 64 |A street in Altd|
000005b0 6f 72 66 53 63 6f 72 65 3a 20 30 4d 6f 76 65 73 |orfScore: 0Moves|
000005c0 3a 20 30 41 72 65 20 79 6f 75 20 73 75 72 65 20 |: 0Are you sure |
000005d0 79 6f 75 20 77 61 6e 74 20 74 6f 20 71 75 69 74 |you want to quit|
000005e0 3f 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 |? |
000005f0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | |
*
00000630 20 20 41 20 73 74 72 65 65 74 20 69 6e 20 41 6c | A street in Al|
00000640 74 64 6f 72 66 53 63 6f 72 65 3a 20 30 4d 6f 76 |tdorfScore: 0Mov|
00000650 65 73 3a 20 30 |es: 0|
00000655
When I run the
fizmo-consolecommand as packaged in Debian/Ubuntu, the status bar messages appear after the>prompts, separated by a row of spaces.I'm not sure if this is just a naïve stripping of control codes from the curses version, but it does present unusual challenges for automation. For example, we can't just time out on
select()of the program'sstdoutand make sure it ends in\n>to be sure it's ready for input.This is fine and easy to prepare for in advance, but a little documentation of exactly what we should be watching for would be helpful. I'd also appreciate an option to have status bar text sent somewhere else, such as
stderr, where it could be handled separately.Just as an example, here's the tail end of a hex dump (eliding repeated lines of spaces) of the output of
fizmo-console Tell.z5from the Inform 6 IBG sample games, where I just started it up and then typedquit\nyes\n: