Repository navigation
Running Programs
Once the editor launches, we should see an tab open for each file specified either in a .ok file or by passing parameters into --files. If no parameters were passed into --files, then files can be opened by pressing the "Open" button in the global header.
To run a program, press "Run" in the editor toolbar. An output console should open, if one is not already open. Output consoles are associated with their file. Multiple consoles can be opened, corresponding to each file that is open. However, if a file is closed, its corresponding console will be automatically closed as well. When typing in an editor, autocomplete should be enabled. Standard functionality such as undo/redo and find/replace are available using the expected keyboard shortcuts. The editor will autosave every 5 seconds, or if the "Save" button in the editor toolbar is pressed.
Pressing "Environments" / "Debug" before a program is run will not work, since the debugger requires a program trace to be generated first. See the relevant sections for more details.
Pressing "Reformat" will reformat the text in the current editor window (but not code in other windows, or commands entered in the output console) if it can be parsed by Scheme. See the relevant section for more details.
Pressing "Test" on a testable file (i.e. one specified in a .ok file or as an argument to --files) will test all files currently open. See the relevant section for more details.
Output consoles will automatically display a warning if the file they are executing is modified. However, this warning will not prevent interaction with the console. Clicking anywhere in the output console will allow commands to be executed within a Scheme session. The up and down arrows allow for navigation within the console history. Multiline console commands can be entered, by pressing enter somewhere other than the end of a line.
The keyboard shortcut Ctrl-Enter/Cmd-Enter will execute the text in the current input field as a Scheme program, both in an editor and in an output console. The file will be manually saved when Ctrl-S/Cmd-S is pressed.