Doug Hellmann

Travis-CI is configured now, but only for linters. We need some unit tests.

Add a builtin for "python" and "python3" that starts an interpreter prompt cycle that runs python statements instead of shelling out. Can we use the cmd module for that?

Test with programs that have progress bar output

3

Git clone or curl for example. Probably need to do some basic handling for control characters like backspace and line feed

the default is to inset a block of text for a command, with the output reading top down. It might be useful for longer output to insert lines to produce...

fix output mingling between commands

1

All commands effectively run in the background now. Either block until a command is done or at least figure out which output block the output should go into instead of...

It’s not really clear what they might be for. Would probably have to associate a name with a python function to make it useful

Let them control which shell we exec in case they want to use special syntax or feature

Let users configure the colors. Maybe ship a few predefined themes

Add it to the readme for now and use it on the main page of the docs when those exist

preserve local toc info for template authors

1

We overwrite the "toc" value in the template context without preserving the old values. We should save them as "localtoc" or something similar so template authors can use the information...