Andrew Plotkin

I've implemented some of a logging feature, but there's no UI to activate it.

This is harder than it looks. A glksave file is player-managed (see http://eblong.com/zarf/glk/terp-saving-notes.html) which means it can only be loaded after the game is up, running, and at a `@save`...

We'd have to stash a copy of the .ulx file in case the player has moved it. Also, does a standard glksave file have enough info to locate our autosave...

Gets important when we build a game-bound app!

Lectote uses a least-common-feature display engine which does not support text colors.

This will look like the Build interface, but it should be under admin.

Dave Cornelson contributes this modified makedist.py for Windows. I haven't tested it or even looked at it much, but it may help somebody as a temporary measure. https://gist.github.com/erkyrath/a599765cdc3e2a17e3726d0d6cee9f51

This is down to the game code or the interpreter code, depending on what IF engine you're talking about. Lectrote (and quixe/glkote) have a file-reading API. I can't remember offhand...

I forgot to follow up on this... @curiousdannii is correct that this is a electrofs issue. I don't see a node core call to convert line breaks, which is not...

This is an easy change: (in the DIRTY_TOOL section of generate_update) ``` ctx = EvalPropContext(task, loctx=loctx, level=LEVEL_DISPLAY) ``` Unfortunately, this reveals a hidden assumption in the property-dependency code -- the...