History

Virgil Dupras 3171b03335 Allow list to stop spitting a line early If a line has a char below 0x20, we consider the line ended, we stop the EMIT loop for this line and spit our NL. This makes LIST stop wasting rows in environments with a tight screen.		2020-11-08 16:47:33 -05:00
..
.gitignore
avra.sh	Add alias and switch word types	2020-10-28 15:02:06 -04:00
forth.bin	Allow list to stop spitting a line early	2020-11-08 16:47:33 -05:00
forth.c
Makefile	emul+cvm: link to curses instead of ncurses	2020-11-07 08:45:26 -05:00
README.md	emul+cvm: link to curses instead of ncurses	2020-11-07 08:45:26 -05:00
stage.c
vm.c	Add word ROT>	2020-10-29 12:41:08 -04:00
vm.h	recipes/rc2014: move recipe blocks into local overlay	2020-09-20 10:50:13 -04:00
xcomp.fs	Add word ROT>	2020-10-29 12:41:08 -04:00
zasm.sh	Add alias and switch word types	2020-10-28 15:02:06 -04:00

README.md

C VM

This is a C implementation of Collapse OS' native words. It allows Collapse OS to run natively on any POSIX environment.

Requirements

You need curses to build the forth executable.

Build

Running make will yield forth and stage executables.

Usage

To play around Collapse OS, you'll want to run ./forth. Type 0 LIST for help.

The program is a curses interface with a limited, fixed size so that it can provide a AT-XY interface.

You can get a REPL by launching the program with rlwrap(1) like this:

rlwrap -e '' -m -S '> ' ./forth /dev/stdin

Problems?

If the forth executable works badly (hangs, spew garbage, etc.), it's probably because you've broken your bootstrap binary. It's easy to mistakenly break. To verify if you've done that, look at your git status. If forth.bin is modified, try resetting it and then run make clean all. Things should go better afterwards.

A modified blkfs can also break things (although even with a completely broken blkfs, you should still get to prompt), you might want to run make pack to ensure that the blkfs file is in sync with the contents of the blk/ folder.

If that doesn't work, there's also the nuclear option of git reset --hard and git clean -fxd.

If that still doesn't work, it might be because the current commit you're on is broken, but that is rather rare: the repo on Github is plugged on Travis and it checks that everything is smooth.