2025-08-30 00:01:31 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 2025-08-30 00:01:56 cool! can you change part of a line? 2025-08-30 00:02:20 Not that easily but if lines are 32 chars it's not a big issue 2025-08-30 00:03:01 If you really want you could do e.g. CHAR ' LIN @ LINE 24 + C! to set char offset 24 on current line to ' 2025-08-30 00:03:35 It's a work in progress, I'll probably add more to it and have some room in the block to do so 2025-08-30 00:03:44 I see 2025-08-30 00:04:02 It doesn't need to stay in one block either but I like that it feels pretty featureful for just one block 2025-08-30 00:04:10 agreed 2025-08-30 00:04:31 I'm mostly happy with how it's handling the limited screen space of the spectrum 2025-08-30 00:05:43 I'm considering adding a word that lets you pre-populate the input buffer, and generally better keyboard controls of the input buffer 2025-08-30 00:05:54 If I do that then adding a word to 'edit' the current line is trivial 2025-08-30 00:06:44 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 2025-08-30 00:06:49 But also good for an editor 2025-08-30 00:12:17 Next thing is to actually make blocks work 2025-08-30 00:14:36 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... 2025-08-30 10:45:19 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 2025-08-30 10:45:47 Useful to have it in a block too, can edit and execute from there easily 2025-08-30 10:46:19 In the spectrum it would be in an array because block invalidation forces the user to go grab a cassette recorder 2025-08-30 15:37:13 forth in action http://patricia.benedetto.free.fr/cornichon.gif