1354161a36
Among other things, we turned off the trace to significantly speed up the debug cycle. State as of https://merveilles.town/@akkartik/106079258606146213 Ohhh, as I save the commit I notice a big problem: I've been editing the disk image directly because writes to the Mu disk lose indentation. But I've been forgetting that the state in the Mu disk needs to be pre-evaluated. So function bindings need extra parens for the environment. The `pixel` calls in the previous commit message are the first statement in the body, and they aren't actually considered part of the body right now. No wonder they don't run. There are lots of other problems, but this will clarify a lot. |
||
|---|---|---|
| .. | ||
| README.md | ||
| cell.mu | ||
| evaluate.mu | ||
| gap-buffer.mu | ||
| global.mu | ||
| grapheme-stack.mu | ||
| main.mu | ||
| parse.mu | ||
| print.mu | ||
| read.mu | ||
| sandbox.mu | ||
| tokenize.mu | ||
| trace.mu | ||
| vimrc.vim | ||
README.md
A prototype shell for the Mu computer
Currently runs a tiny subset of Lisp. Steps to run it from the top-level:
- Build it:
$ ./translate shell/*.mu # generates code.img
- Run it:
$ qemu-system-i386 code.img
or:
$ bochs -f bochsrc
To save typing in a large s-expression, create a secondary disk for data:
$ dd if=/dev/zero of=data.img count=20160
Load an s-expression into it:
$ echo '(+ 1 1)' |dd of=data.img conv=notrunc
Now run with both code and data disks:
$ qemu-system-i386 -hda code.img -hdb data.img
or:
$ bochs -f bochsrc.2disks
You can type in expressions, hit ctrl-s to see their results, and hit Tab
to focus on the ... below and browse how the results were computed. Here's
a demo. The bottom of
the screen shows context-dependent keyboard shortcuts (there's no mouse in the
Mu computer at the moment).
Known issues
-
There's no way to save to disk.
-
Don't press keys too quickly (such as by holding down a key). The Mu computer will crash (and often Qemu will segfault).