| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Front-loads it a bit more than I'd like, but the payoff is that other
recipes will now be able to describe the type checks right next to their
operation.
I'm also introducing a new use of /raw with literals to indicate unsafe
typecasts.
|
| | |
|
| |
|
|
|
| |
How the heck was this working until now?
There must be redundant moves. And was I clobbering test data?
|
| |
|
|
| |
Thanks Jack and Caleb Couch for the idea.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Layer 2 provides an almost fully functioning interactive editor:
$ ./mu edit/00[12]* -- abcdef
|
| |
|
|
|
|
|
|
|
| |
Takes the text to render inside the editor on the commandline:
$ ./mu edit/001-editor.mu -- abcdef
Layer 1 has no interactivity. Just shows the text you pass in on the
commandline, wrapping as you would expect. Press any key to exit.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
`render-string` (and `render-code-string`; ugh) should start a new line
after, not before, like everybody else.
I've been meaning to fix this for a long time, but now I have to, to
move the warnings fields out of early layers.
|
| | |
|
| |
|
|
|
| |
Starting on making the basic programming environment oblivious to
warnings. That should come later.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
To run just until say layer 6, say this:
$ ./mu test edit/00[0-6]*
The layers are not perfect yet; there might be a few things (like the
warning fields) that need to move to a later layer.
|
|
|
Now you can bring up the programming environment by saying:
$ mu edit
The files under edit aren't yet *layers*, though, they have a few
dependencies that we need to clean up.
|