That’s a good idea. Will do.
No, I’m afraid not really, apart from asking the author to use commands like ``print 399 as a rulebook.‘’
Hmm, probably. I’ll have to think about the right way to do that, and it also depends on what happens with Zarf’s idea for in-ulx debug data.
Also on that topic, I’m thinking that it would be nice to have (1) automatic breakpoints on illegal Glk behavior, like those on runtime problems, and (2) commands like break on output'' or break when `foo’ is printed.‘’ They should both be possible.
As you can maybe tell, I haven’t had much time to work on the extensions—I still haven’t gotten to some of Ron’s feedback. But I appreciate the comments, and I’ll try to get the changes in as soon as I have a chance.