2023-04-14 11:50:25 <KipIngram   > Looks like that's just emitting from the stack, right?
2023-04-14 11:51:08 <KipIngram   > Are [DO] and [LOOP] interpreter capable DO LOOP?
2023-04-14 11:58:09 <KipIngram   > I just decided I needed a "reminder system" that actually WORKS for me.  Google calendar - I don't look at it regularly enough.  My phone; there's just something about the way it works that isn't convenient.
2023-04-14 11:58:45 <KipIngram   > Then I realized I have this little neglected box down at the bottom of my console screen - it's there because just to its left I have that power consumption moinitor that I run.  It's about an inch and a half high and maybe four inches wide.
2023-04-14 11:58:48 <KipIngram   > Perfect.
2023-04-14 11:59:17 <KipIngram   > so I just whipped up a little simple Python utility to run there that periodically gets the data and scans a file of one-line reminder records.
2023-04-14 11:59:41 <KipIngram   > It just prints the reminder part of each line in that window if "today" matches the hit spec for the reminder.
2023-04-14 12:00:02 <thrig       > seems like this could be better done with an Electron app
2023-04-14 12:00:17 <KipIngram   > I can already tell this will work, because I spend a lot of time on this screen and it will get my attention if something shows up down there.
2023-04-14 12:00:24 <KipIngram   > Could be, but I don't know Electron.
2023-04-14 12:00:37 <KipIngram   > I'd have spent more time learning it than it took me to write this.
2023-04-14 12:01:32 <KipIngram   > I just bought portable battery jump units for our cars - I want to have a reliable reminder to top them all off once a month or so.
2023-04-14 12:02:47 <KipIngram   > And while I was at it I tossed in a reminder for the days of the week I'm in charge of dinner, because I tend not to remember until late afternoon and then it's a pain.
2023-04-14 12:03:24 <KipIngram   > But if I think about it as soon as I'm up and working in the morning then I have time to think about it and make a plan.
2023-04-14 12:04:13 <KipIngram   > I don't expect to have some huge list; there's room in the box for seven things and I think that will always be enough.
2023-04-14 12:04:35 <KipIngram   > I didn't write in any way to clear "done" items - they just s how up for the duration of that day and then go away.
2023-04-14 12:04:58 <thrig       > (that was humor; Electron apps are notably... bloated and slow)
2023-04-14 14:06:47 <unjust      > KipIngram: if that was about the message that i wrote a few days back, yes that's exactly what they are
2023-04-14 16:26:05 <unjust      > so gforth implements [DO] and [LOOP] as something like:
2023-04-14 16:26:13 <unjust      > VARIABLE <INDEX>
2023-04-14 16:26:22 <unjust      > : <DO> >IN @ -ROT DO I <INDEX> ! DUP >R >IN ! INTERPRET R> SWAP +LOOP DROP ; IMMEDIATE
2023-04-14 16:26:29 <unjust      > : <LOOP> 1 RDROP ; IMMEDIATE
2023-04-14 16:28:26 <unjust      > ( paraphrased using VARIABLE <INDEX> instead of gforth's CODE word USERADDR which returns a memory location )
2023-04-14 16:28:46 <unjust      > 67 66 65 3 0 <DO> <INDEX> @ . EMIT SPACE <LOOP> 0 A 1 B 2 C  ok
2023-04-14 16:29:41 <unjust      > but this hinges on being able to modify the value of >IN, which it doesn't work in pForth
2023-04-14 16:31:31 <unjust      > what other approaches could be used to implement [DO] ... [LOOP] ?