Now I struggle to remember why I ever did things they way I did.
There must have been a reason...

Usage of "LIST" wasn't explicit enough for a complete newcomer. I
hope that with this wording, anyone can figure out how to navigate
blocks and learn the system.

Not yet tried on real hardware, but we should be getting pretty
close...

Yup, it was a deja vu. I remember now.

There's a bug where the first char after a-lock isn't a-modded. I
have troubles figuring it out for now. It feels like deja vu. I
think I had the same problem with asm.

Pushed all words directly interfacing with ports and memory offsets to
low level layers. This saves us the need for keeping those variables in
runtime memory.

The goal is to insert device drivers in between.

That makes it easier to write drivers that can be xcompiled.

In emulator of course...

On the emulator of course...

Gave more priority to CPU in the emulator because initialization would
otherwise be horrendously slow.

I need RSHIFT and LSHIFT first...

Also, delay the shadowing of DO..LOOP's I for as long as possible.

Make it print edited line and also have it adjust cursor pos.

Also, made LIST properly handle full 64-chars lines not ending with
a null or CR. Previously, such a line would be accompanied by its
following line, duplicating that line's output.

This allows us to make DO..LOOP more compact.

This was caused by the removal of signed-ness a long while ago.

I'd like to move this code, along with all recipe contents, to blk/.
It's easier if "emul-related" code is gathered at the same place.

Lines edited with the Block editor end with 0xd and (print) spits
spurious CR when printing those lines.

Also, properly initialize ACC in BROWSE.

And use them in all places they make sense.

There was a weird empty block in the middle of the program.

I removed it because it was redundant with Starting Forth, but
I directly reference it in the dictionary, so well...

With this tool, we can send content to a TRS-80 directly to floppy.
This paves the way to writing ourselves a set of disks containing the
blkfs!