9dcbec398c
Standardize quotes around reagents in error messages. I'm still sure there's issues. For example, the messages when type-checking 'copy'. I'm not putting quotes around them because in layer 60 I end up creating dilated reagents, and then it's a bit much to have quotes and (two kinds of) brackets. But I'm sure I'm doing that somewhere.. |
||
|---|---|---|
| .. | ||
| 001-editor.mu | ||
| 002-typing.mu | ||
| 003-shortcuts.mu | ||
| 004-programming-environment.mu | ||
| 005-sandbox.mu | ||
| 006-sandbox-copy.mu | ||
| 007-sandbox-delete.mu | ||
| 008-sandbox-edit.mu | ||
| 009-sandbox-test.mu | ||
| 010-sandbox-trace.mu | ||
| 011-errors.mu | ||
| 012-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.