00:01:31
##forth
<veltas>
What's funny is I put the block near the attributes (colour) page, so if I accidentally go slightly out of bounds I change all the colouring
00:01:56
##forth
<xentrac>
cool! can you change part of a line?
00:02:20
##forth
<veltas>
Not that easily but if lines are 32 chars it's not a big issue
00:03:01
##forth
<veltas>
If you really want you could do e.g. CHAR ' LIN @ LINE 24 + C! to set char offset 24 on current line to '
00:03:35
##forth
<veltas>
It's a work in progress, I'll probably add more to it and have some room in the block to do so
00:03:44
##forth
<xentrac>
I see
00:04:02
##forth
<veltas>
It doesn't need to stay in one block either but I like that it feels pretty featureful for just one block
00:04:10
##forth
<xentrac>
agreed
00:04:31
##forth
<veltas>
I'm mostly happy with how it's handling the limited screen space of the spectrum
00:05:43
##forth
<veltas>
I'm considering adding a word that lets you pre-populate the input buffer, and generally better keyboard controls of the input buffer
00:05:54
##forth
<veltas>
If I do that then adding a word to 'edit' the current line is trivial
00:06:44
##forth
<veltas>
The point of a pre-populated input buffer for me is that it would be useful for a lot of user interfaces, and for command-line history
00:06:49
##forth
<veltas>
But also good for an editor
00:12:17
##forth
<veltas>
Next thing is to actually make blocks work
00:14:36
##forth
<xentrac>
yeah, if you had like a circular buffer of recently typed interpret-mode lines from which you could copy lines to whatever block you were working on...
10:45:19
##forth
<veltas>
xentrac: On a normal forth I'd consider having a HISTORY var which when non-zero is a block that just circularly receives lines of history in truncated 64 or 128 byte groups
10:45:47
##forth
<veltas>
Useful to have it in a block too, can edit and execute from there easily
10:46:19
##forth
<veltas>
In the spectrum it would be in an array because block invalidation forces the user to go grab a cassette recorder