| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
| |
Minor issue in building until just layer 32.
|
| |
|
|
|
|
|
|
|
| |
No, 2001 is no good. Phony targets can't early-exit if everything's
built. New approach:
$ CFLAGS=-g make && ./mu test
etc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Let's stop hackily editing compiler flags in makefile.
I considered modifying the 'mu' script as well, with cases like this:
1. mu test -- don't optimize
2. mu test edit.mu -- optimize
3. mu test edit.mu just-one-test -- don't optimize
4. mu edit.mu -- interactive; optimize
5. mu -- just help message; don't optimize
But that seems brittle for all the added complexity. From now on to
build quickly just do:
$ make dbg && mu test
etc.
|
| | |
|
| |
|
|
|
| |
Still worth trying to optimize, though. Current lowest-hanging fruit:
stop having index/index-address copy entire arrays around.
|
| |
|
|
|
| |
Spent a while trying to understand why editing a slightly larger program
was so much slower. Then realized I'd managed to disable optimizations.
|
| | |
|
| | |
|
| |
|
|
|
| |
The slowness of the environment -- even for code spanning just a couple
hundred lines -- is the biggest priority right now.
|
| |
|
|
|
| |
Not strictly necessary, but it might help me stage the introduction of
arrays and 'new'.
|
| |
|
|
| |
Thanks Caleb Couch.
|
| | |
|
| | |
|
| |
|
|
| |
Now we can make use of all the depths from 1 to 99.
|
| | |
|
| |
|
|
|
|
| |
This can happen if 'canonize' fails. Make sure it doesn't kill mu.
Thanks Caleb Couch.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Environment much more responsive now. And it doesn't slow down as much
just because I'm on a larger screen.
|
| | |
|
| |
|
|
| |
Thanks Jack and Caleb Couch.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
More friendly way to 'stash' stuff in the trace so that you can toggle
lines of code to see their stashed traces.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Now that we have larger-res images for the Readme they look good even if
the browser is magnified with ctrl-+ (like mine is).
factorial-test.png looks about the same size as surrounding text at
250px wide. Original size is 330px.
factorial.png original size is 450px. So its width should be 340px.
chessboard-test.png original size is 423px. So its width should be
320px.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Also ensure we don't render unnecessarily.
This is really where I want a formal type-like system to help me.
All functions have paired calls to hide-screen and show-screen, except
for the one in main.
Only functions at the 'topmost' level are expected to hide/show.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Thanks Caleb Couch.
|
| |
|
|
|
|
|
| |
It took me a long time to fix termbox because the escape codes it was
seeing seemed all wrong. Had to stop calling tb_shutdown/printf and put
in the extra 3 lines to log to a file. Then everything cleared up.
Weird.
|
| |
|
|
|
| |
This was important because somebody connecting on tmux would mess up the
environment.
|
| |
|
|
| |
Standardize test names.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Worrisome that I'm not adding a test here. Still not convinced I have
the right set of tests. There's certainly still breakage when I run
tests manually. Perhaps I should test all combinations of arrow keys and
page-up/page-down. That's 36 tests for 2-combinations..
|
| |
|
|
|
| |
The old approach with cached page starts doesn't work when you mix
scrolling by line and page.
|
| |
|
|
|
|
| |
(#1 was previous commit)
Thanks Caleb Couch.
|
| | |
|