collapseos/blk/084

CURRENTPTR points to current CURRENT. The Forth CURRENT word
doesn't return RAM+2 directly, but rather the value at this
address. Most of the time, it points to RAM+2, but sometimes,
when maintaining alternative dicts (during cross compilation
for example), it can point elsewhere.

NLPTR points to an alternative routine for NL (by default,
CRLF).

BLK* see B416.

FUTURE USES section is unused for now.          

DRIVERS section is reserved for recipe-specific drivers.
Replace the "> " prompt with the more traditional "ok" one This is more than cosmetic, it's also highly usable. The presence or absence of the "ok" message allows us to know whether the command aborted. Previously, the "> " prompt appeared when the system expected a prompt in the INTERPRET context, whether the previous command aborted or not. Also, this allows us to get rid of that ugly FLAGS global variable. 2020-04-25 02:10:07 +10:00			`CURRENTPTR points to current CURRENT. The Forth CURRENT word`
			`doesn't return RAM+2 directly, but rather the value at this`
			`address. Most of the time, it points to RAM+2, but sometimes,`
			`when maintaining alternative dicts (during cross compilation`
			`for example), it can point elsewhere.`

Add word NL 2020-05-04 22:10:18 +10:00			`NLPTR points to an alternative routine for NL (by default,`
			`CRLF).`

Make blk use system RAM 2020-05-15 04:49:16 +10:00			`BLK* see B416.`
Move notes.txt in blk 2020-04-15 04:25:14 +10:00
Make blk use system RAM 2020-05-15 04:49:16 +10:00			`FUTURE USES section is unused for now.`
Move notes.txt in blk 2020-04-15 04:25:14 +10:00
Make blk use system RAM 2020-05-15 04:49:16 +10:00			`DRIVERS section is reserved for recipe-specific drivers.`
tools: add blkunpack and remove cfspack, which will not ever be used again. 2020-04-17 09:44:17 +10:00
VE: add 't' This is the first commit I do entirely in VE. It's a habit I'm planning on taking as it helps a lot to find usability issues. 2020-06-12 08:12:01 +10:00