| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
Exception: allow run-interactive to continue even if it encounters
errors in parsing its ingredient as mu code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was reading lines like this in scenarios:
-warn: f: error error
as:
-warn: f
which was causing them to be silently ignored.
Also found an insane preprocessor expansion from not parenthesizing
preprocessor arguments. SIZE(end+delim) worked even when end was an
integer, but it happily didn't ever get the wrong answer.
|
|
|
|
| |
Thanks Jack and Caleb Couch for the idea.
|
| |
|
|
|
|
| |
Does nothing useful yet, though.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
Ingredients of 'main' are always strings (type address:array:character),
and are delineated from .mu files to load by a "--", e.g.:
$ ./mu x.mu y.mu -- a b c
Here 'main' must be defined in one of x.mu and y.mu, and will receive
the ingredients "a", "b", and "c".
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
`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.
|
| |
|
|
|
|
|
| |
Follow-up to 2147, which switched transform_all to only run once, after
loading all layers.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This will let me create separate 'main' recipes at each layer so people
can interact with less featureful versions.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
edit.mu is now over 9k lines long. Only 2.6k of them are code. Plan:
chunk it into multiple files inside say an 'edit' directory. Then you
can run it with:
$ mu edit/*
I also want to be able to test just a few layers:
$ mu edit/00[1-5]*
When I try to chunk it into files, the first issue I run into is that
before/after can't refer back to previous layers. Solution:
transform_all at one shot after loading all files.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On slow networks sometimes escape sequences were being partially
consumed, causing junk to be added to the editor when you pressed arrow
keys and so on. Now we have a way to wait.
Empirically seems to work if I page-up and then scroll back up using
up-arrow. Before I'd consistently get junk even on my local machine. Now
I no longer do.
If we still see problems I'll increase the wait time and see if the
increase helps. Then we'll know more about this approach.
|
|
|
|
|
| |
This bit of code is complex enough now that I'm bothered I can't write
tests for has-more-events?
|