It’s been a while so I can’t tell you the exact scenario but we were getting garbled text where we’re printing a description and there’s some additional text or garbage being printed after it. It usually came down to situations where we either were using double quotation marks for dictionary words or not including commas between things that were supposed to have commas, or including commas between things that weren’t supposed to have commas. Maybe @FeSerenity remembers more clearly?
Yeah, those are all possible mistakes. :)
There’s also the one where you write print foo(); when you should have just done foo(); and the output has a mysterious “1” stuck on the end.
1 Like
Throwing my hat into the ring: I’m also playing around with Inform 7 in a plain text editor, and wanted a bundle of Inform 7 binaries I could use, so I made a thing called Inform 7 for Unix Nerds:
There’s a whole infrastructure for building the Inform 7 command-line tools and trying to bundle them together in a useful way, but it also makes a zip archive of pre-built binaries - download that, extract it somewhere, put the bin/ directory onto your $PATH, and then you can have a Makefile that calls inform7 and inform6 as necessary. There’s even an example Makefile you can start from.
There’s still a lot of rough edges; in particular, Writing with Inform and the Inform Recipe Book assume the presence of APIs present in the Inform IDE that aren’t available to a regular browser, and I haven’t figured out how to clean those up.
Nevertheless, I can build a .z8 or .ulx story file from a .i7 input file, so that’s a start.