mu/shell
2021-04-21 21:34:55 -07:00
..
cell.mu start cleaning up pixel graphics 2021-04-19 10:47:30 -07:00
evaluate.mu shell: non-recursive 'while' 2021-04-21 21:34:55 -07:00
gap-buffer.mu start cleaning up pixel graphics 2021-04-19 10:47:30 -07:00
global.mu shell: refuse to 'def' duplicate names 2021-04-21 20:54:18 -07:00
grapheme-stack.mu start cleaning up pixel graphics 2021-04-19 10:47:30 -07:00
life.mu . 2021-04-17 23:59:30 -07:00
main.mu clear old output when new run is in progress 2021-04-21 20:06:46 -07:00
parse.mu parse dotted lists 2021-04-15 19:47:01 -07:00
print.mu . 2021-04-18 23:10:01 -07:00
read.mu bump up the token limit again 2021-04-17 22:35:35 -07:00
README.md . 2021-04-16 20:26:56 -07:00
sandbox.mu clear old output when new run is in progress 2021-04-21 20:06:46 -07:00
tokenize.mu shell: dot token 2021-04-15 08:48:53 -07:00
trace.mu start cleaning up pixel graphics 2021-04-19 10:47:30 -07:00
vimrc.vim 7842 - new directory organization 2021-03-03 22:21:03 -08:00

A prototype shell for the Mu computer

Currently runs a tiny subset of Lisp. Steps to run it from the top-level:

  1. Build it:
$ ./translate shell/*.mu      # generates code.img
  1. 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).