Yeah, that's a good question. Even though the mu core is at the top directory, there are a couple of apps in sub-directories of their own. To run a single-file

Yeah, that's a good question. Even though the mu core is at the top directory, there are a couple of apps in sub-directories of their own. To run a single-file mu program you say: $ ./mu factorial.mu To run a more complex app, you just give a directory name rather than a filename: $ ./mu edit Files inside the directory are loaded in numeric order just like at the top level. You can also run just a subset of the layers for the editor: $ ./mu test edit/001* $ ./mu test edit/00[12]* $ ./mu test edit/00[1-3]* (Notice how the number of tests/dots grows at each layer.) Since the layers are just regular files there's nothing stopping you from rewriting history as much as you want. That ability was precisely what I built them for. I've only recently started using directories, so I'm sure there's stuff here I haven't considered. Feedback most welcome.