3151fb2387
It also seems useful that the number maps to the name of the file the sandbox is saved in. However this mapping is currently a happy accident and not actually tested. I'm starting to switch gears and help make the editor useable with many many sandboxes. This is just the first step of several. |
||
|---|---|---|
| .. | ||
| 001-editor.mu | ||
| 002-typing.mu | ||
| 003-shortcuts.mu | ||
| 004-programming-environment.mu | ||
| 005-sandbox.mu | ||
| 006-sandbox-edit.mu | ||
| 007-sandbox-delete.mu | ||
| 008-sandbox-test.mu | ||
| 009-sandbox-trace.mu | ||
| 010-warnings.mu | ||
| 011-editor-undo.mu | ||
| mu_run | ||
| Readme.md | ||
| tmux.conf | ||
Variant of the mu programming environment that runs just the sandbox.
Suitable for people who want to run their favorite terminal-based editor with mu. Just run editor and sandbox inside split panes atop tmux. For example, here's mu running alongside vim:
To set this up:
a) copy the lines in tmux.conf into $HOME/.tmux.conf.
b) copy the file mu_run somewhere in your $PATH.
Now when you start tmux, split it into two vertical panes, run mu sandbox on
the right pane and your editor on the left. You should be able to hit F4 in
either side to run the sandbox.
Known issues: you have to explicitly save inside your editor before hitting F4, unlike with 'mu edit'.
One problem with a fork of the edit/ app is that many of the tests write to the same files under the .traces/ directory. I try to always commit the results of edit/ rather than the sandbox/ app, but I haven't been perfect.