Accommodate user input

[ilectra]

The command the user runs and wants to document, might request input from the user. Have to accommodate this!

[ajjackson]

The simplest approach to this might be to treat each user interaction as a separate input/output "command" pair? This requires no additional syntax, and may work with the wizard implementation. The key difference is that we are defining the separation of blocks as "whenever the user gets a prompt" rather than "whenever a foreground process finishes running."

[ajjackson]

The latter is probably easier to detect but the former may be more intuitive, especially for novices?

[giordano]

Related to this issue, it may happen that the tutorial suggests to open a program which requires interaction to exit. For example, https://github.com/swcarpentry/shell-novice/blob/gh-pages/_episodes/03-create.md runs nano to edit a file. This might also expect that students will write something to the file.