[2024-04-18] 6yo remains home sick (although she's out running around outside and hasn't had a fever all day, so 🤞 on tomorrow), so I'm not getting a whole lot else done. I'm still trying to get my $home/src/cmd/mkfile fixed. It's a mishmash of things imported from a few sources, and I've let it get too much of a mess. Now I can't get it to recognize additional dependencies on targets (like litclock and marquee now depending on wordwrap). I've managed to screw up all my Raspberry Pi SD cards (except the one in my main terminal, which I don't want to mess with) and haven't been able to get either screen I want to use for litclock working. Sigh. Going to keep poking; I'll probably pull an image and start clean, I think. ☐ Fix $home/src/cmd/mkfile. ☐ Start on the hardware incarnation of litclock.
[2024-04-17] Something about my $home/src/cmd/mkfile is messed up. I noticed it while putting in the rules for litclock and marquee, but whatever's wrong is more general than that. It's also a mess. Let's fix it up. Now that I've done all this stuff for litclock, marquee, and wordwrap, they really want man pages. I want litclock to run on a hardware version; initially a Raspberry Pi and screen I already have in a case (although it's cheap plastic and I'd like to get something nicer eventually). Start on that. ☐ Fix $home/src/cmd/mkfile. ☑ Give litclock, marquee, and wordwrap man pages. ☐ Start on the hardware incarnation of litclock.
[2024-04-16] IWP9 was great. Yay Glenda! In addition to the wonderful talks, I got litclock more-or-less working while I was there (mostly in the two windows between the hotel and an airplane). It ran and did what I was after, but was buggy. Things have been slow since my return due to a sick kiddo, but I've put on some more polish and extracted the wordwrapping bits shared by litclock and marquee into a little one-function library. I'm now pretty happy with all that, although there's one more bit I'm considering moving from litclock.c to wordwrap.c. [2024-04-17] Something about my $home/src/cmd/mkfile is messed up. I noticed it while putting in the rules for litclock and marquee, but whatever's wrong is more general than that. It's also a mess. Let's fix it up. Now that I've done all this stuff for litclock, marquee, and wordwrap, they really want man pages. I want litclock to run on a hardware version; initially a Raspberry Pi and screen I already have in a case (although it's cheap plastic and I'd like to get something nicer eventually). Start on that. ☐ Fix $home/src/cmd/mkfile. ☐ Give litclock, marquee, and wordwrap man pages. ☐ Start on the hardware incarnation of litclock.
[2024-04-11] Gah. I spent like an hour yesterday convinced I had forgotten something fundamental about how either fork() or pipe() worked. Just could not get anything sensible happening. Walked away in frustration. Looked back at it today, and it took 1 minute to see the misplaced 'break' I'd read past dozens of times. 🤦 Anyway, litclock does the basic display part now! Moving on... ☑ Get litclock displaying the quotes from the list. ☑ Move the word wrapping bits to a function. ☐ Get it to refresh on a timer. ☐ Make litclock highlight the "time" part of the quote. ☐ Make litclock put the work and author in the right font. ☐ Do something smarter with font selection, cross-platform? ☐ Same for finding 'look'. Bah. [2024-04-12] IWP9! I missed last year, so it's still been... what, most of a decade for me? *Very* excited.
[2024-04-09] Back in the habit. Rough couple weeks, but cleared a bunch of client backlog work. Feeling back on track. I had kinda wanted to do World Naked CSS Day, but I'm punting on that. Too much to do before I get on a plane. I want to see if I can get litclock going before IWP9. This *should* be doable, although some of the font selection/placement/layout stuff is tricky. ☐ Get litclock displaying the quotes from the list. [2024-04-10] More litclock work, probably font positioning & highlighting. ☐ Make litclock put the work and author in the right font. ☐ Make litclock highlight the "time" part of the quote.
I'm single parenting this week, so I'm mostly giving myself the week "off". I'm hoping to finish the City Fresh bug triage, do some web cleanup, and maybe a little progress on my litclock. To much personal life stuff to take care of beyond that.
[2024-03-08] Punting on City Fresh login issues for now; ball's in their court. And we skipped yesterday's meeting, but I still need to do the bug triage. Putting the /src index up yesterday was good; lets put some proper links and a header or footer on there. ☐ KaleChips bug triage. ☐ Header and/or footer on the /src page. ☐ Make sure the links elsewhere on the web make sense.
[2024-03-07] For City Fresh: schedule some time with Anna Kiss and/or Leah to figure out why they can't ever seem to get into our servers. Then finish the bug triage so I can get some things in place before the season starts. Something's busted in my 'marquee' program around redrawing: only the first word (?) gets printed after the first draw. Let's track that down. Then I think the only thing for that to be "done" is adding newline handling. Then publish it somewhere. Thinking about 'marquee' and datefmt (for yesterday's lab report) reminded me I don't have a place to put the little one-offs I make that I like. A separate entry on txtpunk for 'marquee' seems like overkill, and I want a local place for utilities like datefmt. Maybe finally time for that. ☐ Figure out why leah can never get logged in (can AK?). ☐ KaleChips bug triage. ☐ Fix the redraw bug in 'marquee'. ☐ Handle newlines in the input to 'marquee'. ☐ Put 'marquee' on txtpunk (for now?). ☐ Sketch out a way to put small code utilities online.
[2024-03-06] I got the 'daily' writeup done yesterday, but found I don't seem to have a troff font which has the checkbox characters in it. Let's fix that and get it published. After some time away from it, I need to get back to KaleChips work. Most urgently an order form update, and we need to figure out why they can never get logged in when they need to (operator error?). Then a bug triage before Thursday. Since I last wrote about it, I've gotten my 'marquee' program displaying text properly, including recognizing resize events, but there's something busted about the redraw: only the first word (?) gets printed after the first time. Let's track that down. Then I think the only thing for that to be "done" is adding newline handling. Then publish it somewhere. In starting the lab report, I'm reminded I don't have a system for publishing the little one-offs I make that I like. A separate entry on txtpunk for 'marquee' seems like overkill, and I want a local place for utilities like datefmt. Maybe finally time for that. ☑ Fix font issue in "daily" lab report. ☑ Get the "daily" lab report published. ☑ Fix City Fresh order form. ☐ Figure out why leah can never get logged in (can AK?). ☐ KaleChips bug triage. ☐ Fix the redraw bug in 'marquee'. ☐ Handle newlines in the input to 'marquee'. ☐ Put 'marquee' on txtpunk. ☐ Sketch out a way to put small code utilities online. [2024-03-07] For City Fresh: schedule some time with Anna Kiss and/or Leah to figure out why they can't ever seem to get into our servers. Then finish the bug triage so I can get some things in place before the season starts. Something's busted in my 'marquee' program around redrawing: only the first word (?) gets printed after the first draw. Let's track that down. Then I think the only thing for that to be "done" is adding newline handling. Then publish it somewhere. Thinking about 'marquee' and datefmt (for yesterday's lab report) reminded me I don't have a place to put the little one-offs I make that I like. A separate entry on txtpunk for 'marquee' seems like overkill, and I want a local place for utilities like datefmt. Maybe finally time for that. ☐ Figure out why leah can never get logged in (can AK?). ☐ KaleChips bug triage. ☐ Fix the redraw bug in 'marquee'. ☐ Handle newlines in the input to 'marquee'. ☐ Put 'marquee' on txtpunk (for now?). ☐ Sketch out a way to put small code utilities online.
[2024-03-05] Today I'm writing up a lab report on this 'daily' system, mostly so I can stop thinking about it. Did most of that yesterday, before getting distracted. Also publish the associated files. Since I last wrote about it, I've gotten my 'marquee' program displaying text properly, including recognizing resize events, but there's something busted about the redraw: only the first word (?) gets printed after the first time. Let's track that down. Then I think the only thing for that to be "done" is adding newline handling. Then publish it somewhere. In starting the lab report, I'm reminded I don't have a system for publishing the little one-offs I make that I like. A separate entry on txtpunk for 'marquee' seems like overkill, and I want a local place for utilities like datefmt. Maybe finally time for that. After some time away from it, I need to get back to KaleChips work. Most urgently an order form update, and we need to figure out why they can never get logged in when they need to (operator error?). Then a bug triage before Thursday. ☐ Write up "daily" lab report. ☑ Publish mkfile, cf, and f for 'daily'. ☐ Fix the redraw bug in 'marquee'. ☐ Handle newlines in the input to 'marquee'. ☐ Put 'marquee' on txtpunk. ☐ Sketch out a way to put small code utilities online. ☐ Fix City Fresh order form. ☐ Figure out why leah can never get logged in (can AK?). ☐ KaleChips bug triage. [2024-03-06] I got the 'daily' writeup done yesterday, but found I don't seem to have a troff font which have the checkbox characters in it. Let's fix that. Since I last wrote about it, I've gotten my 'marquee' program displaying text properly, including recognizing resize events, but there's something busted about the redraw: only the first word (?) gets printed after the first time. Let's track that down. Then I think the only thing for that to be "done" is adding newline handling. Then publish it somewhere. In starting the lab report, I'm reminded I don't have a system for publishing the little one-offs I make that I like. A separate entry on txtpunk for 'marquee' seems like overkill, and I want a local place for utilities like datefmt. Maybe finally time for that. After some time away from it, I need to get back to KaleChips work. Most urgently an order form update, and we need to figure out why they can never get logged in when they need to (operator error?). Then a bug triage before Thursday. ☐ Fix font issue in "daily" lab report and publish it. ☑ Publish mkfile, cf, and f for 'daily'. ☐ Fix the redraw bug in 'marquee'. ☐ Handle newlines in the input to 'marquee'. ☐ Put 'marquee' on txtpunk. ☐ Sketch out a way to put small code utilities online. ☐ Fix City Fresh order form. ☐ Figure out why leah can never get logged in (can AK?). ☐ KaleChips bug triage.
[20240304] Today I'm writing up a lab report on this 'daily' system, mostly so I can stop thinking about it. Since I last wrote about it, I've gotten my 'marquee' program displaying text properly, including recognizing resize events, but there's something busted about the redraw: only the first word (?) gets printed after the first time. Let's track that down. Then I think the only thing for that to be "done" is adding newline handling. Then publish it somewhere. In starting the lab report, I'm reminded I don't have a system for publishing the little one-offs I make that I like. A separate entry on txtpunk for 'marquee' seems like overkill, and I want a local place for utilities like datefmt. Maybe finally time for that. ☐ Write up "daily" lab report. ☐ Fix the redraw bug in 'marquee'. ☐ Handle newlines in the input to 'marquee'. ☐ Put 'marquee' on txtpunk. ☐ Sketch out a way to put small code utilities online.
[20240212] I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ I'm trying to get a toy "literature clock" working, mostly as practice with graphics(3). Starting with a little "marquee" display, mostly to get the word wrapping right. Inspired by https://literature-clock.jenevoldsen.com. This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. ☐ Evaluate half-finished project inventory for IWP9. ☑ Get a graphics(2) toy displaying something. ☐ Turn that into a "literature clock". ☐ Look at old 'daily' scripts, check for useful overlap.
20240212
2024-02-08 I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ I'm trying to get a toy "literature clock" working, mostly as practice with graphics(3). Starting with a little "marquee" display, mostly to get the word wrapping right. Inspired by https://literature-clock.jenevoldsen.com. This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. ☐ Evaluate half-finished project inventory for IWP9. ☑ Get a graphics(2) toy displaying something. ☐ Turn that into a "literature clock". ☐ Look at old 'daily' scripts, check for useful overlap.
2024-02-05 I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ I'm trying to get a toy "literature clock" working, mostly as practice with graphics(3). I have Inspired by https://literature-clock.jenevoldsen.com. This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. ☐ Evaluate half-finished project inventory for IWP9. ☐ Get a graphics(2) toy displaying something. ☐ Look at old 'daily' scripts, check for useful overlap.
2024-02-05 I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ I'm trying to get a toy "literature clock" working, mostly as practice with graphics(3). I have Inspired by https://literature-clock.jenevoldsen.com. This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. ☐ Evaluate half-finished project inventory for IWP9. ☐ Get a graphics(3) toy displaying something. ☐ Look at old 'daily' scripts, check for useful overlap.
2024-02-05 I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ A little more to do on the wiki and Org Profile for GSoC (one more day...). This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. ☐ Evaluate half-finished project inventory for IWP9. ☑ Review GSoC Org Profile. ☑ Another pass over the wiki, especially the ideas page. ☐ Look at old 'daily' scripts, check for useful overlap.
2024-02-05 I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ A little more to do on the wiki and Org Profile for GSoC (one more day...). This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. ☐ Evaluate half-finished project inventory for IWP9. ☐ Review GSoC Org Profile. ☐ Another pass over the wiki, especially the ideas page. ☐ Look at old 'daily' scripts, check for useful overlap.
2024-02-03 Knocked off the whole list yesterday; amazing what realistic goal setting will do. It's a weekend and I'm single parenting for most of it, so it'll be light. I need to do an inventory of the half-finished projects I was hoping to get turned into IWP9 papers and see what's still realistic for any of them now. ☹ A little more to do on the wiki and Org Profile for GSoC (this will probably be the case until the application deadline hits). [Keeping this here for next week.] This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that... but that can wait until next week. ☐ Evaluate half-finished project inventory for IWP9. ☐ Review GSoC Org Profile. ☐ Another pass over the wiki, especially the ideas page.
2024-02-02 Relatively unproductive day yesterday. Unfortunately I've got a bunch of things blocked in today, too. Let's see about some realistic expectations for today, and punt some stuff until the weekend or next week. I updated/fixed some wiki maintenance scripts, but now I'm getting hourly mail about changes which are just automated noise. Let's get that fixed before I tune it out. I want to finish the first draft of the GSoC application today. The ideas page is where most of the work happens, but obviously this needs to be in. Do the next round of wiki cleanup over the weekend. I'm forcing myself not to over-engineer how I'm generating the web page from the plan archive (no! no it does *not* need an RSS feed!), but I should at least HTML-escape the output so I don't have to worry about it when I'm writing here. A quick test: "<&>" This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that... but that can wait until next week. Still need to get approval for my KaleChips update and deploy it. ☑ Submit first draft of GSoC application. ☑ Fix wiki maintenance notifications not to notify about noise. ☑ HTML-escape the generation of the "plans" page. ☑ Client approval for KaleChips deployment. ☑ Deploy KaleChips update.
2024-02-02 Relatively unproductive day yesterday. Unfortunately I've got a bunch of things blocked in today, too. Let's see about some realistic expectations for today, and punt some stuff until the weekend or next week. I updated/fixed some wiki maintenance scripts, but now I'm getting hourly mail about changes which are just automated noise. Let's get that fixed before I tune it out. I want to finish the first draft of the GSoC application today. The ideas page is where most of the work happens, but obviously this needs to be in. Do the next round of wiki cleanup over the weekend. I'm forcing myself not to over-engineer how I'm generating the web page from the plan archive (no! no it does *not* need an RSS feed!), but I should at least HTML-escape the output so I don't have to worry about it when I'm writing here. A quick test: "<&>" This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that... but that can wait until next week. Still need to get approval for my KaleChips update and deploy it. ☐ Submit first draft of GSoC application. ☑ Fix wiki maintenance notifications not to notify about noise. ☑ HTML-escape the generation of the "plans" page. ☑ Client approval for KaleChips deployment. ☐ Deploy KaleChips update.
2024-02-01 I want to finish the first draft of the GSoC application today. The ideas page is where most of the work happens, but obviously this needs to be in. Also, the rest of the wiki needs another pass; it still says "students" in places where that isn't really appropriate any more, for example. I'm forcing myself not to over-engineer how I'm generating the web page from the plan archive (no! no it does *not* need an RSS feed!), but I should at least HTML-escape the output so I don't have to worry about it when I'm writing here. This whole thing with the plan files feels like I'm re-creating some daily work log/to-do list scripts I used to use a long time ago. I haven't used it regularly since 2015, but they were helpful. Maybe I should give that another shot, or generate this from that. I'd like to get started on a Lab Report for recent work. Still need to get approval for my KaleChips update and deploy it. ☐ Submit first draft of GSoC application. ☐ Wiki cleanup for GSoC-related pages. ☐ HTML-escape the generation of the "plans" page. ☐ Revisit 'daily' log tools. ☐ Lab repot (at least a start). ☐ Client approval for KaleChips deployment. ☐ Deploy KaleChips update.
2024-01-31 The morning's Weird Side Project is a little two-step archiver for these plan files (WHY AM I LIKE THIS?). First, watch for periodic changes and save each version; then, build a web page around those. For today, the "web page" might just be some "pre" tags. (Ugh, I'm going to have to html-escape things, aren't I?) Then another round of wiki cleanup before announcing the Plan 9 Foundation's GSoC application. (Hey look, sneak peak on finger!) Still waiting on client approval before pushing my last round of changes for them; hopefully this evening. ☑ 'keeprev' to keep revisions of the plan file. ☑ Make a simple web page when those are updated. ☑ Another round of wiki cleanup. ☑ Announce Plan 9 applying to GSoC. ☐ Client approval for KaleChips deployment. ☐ Deploy KaleChips update. 2024-02-01 I want to finish the first draft of the GSoC application today. The ideas page is where most of the work happens, but obviously this needs to be in. I'm forcing myself not to over-engineer how I'm generating the web page from the plan archive (no! no it does *not* need an RSS feed!), but I should at least HTML-escape the output so I don't have to worry about it when I'm writing here. I'd like to get started on another Lab Report for recent work. Still need to get approval for my KaleChips update and deploy it. ☐ Submit first draft of GSoC application. ☐ HTML-escape the generation of the "plans" page. ☐ Lab repot (at least a start). ☐ Client approval for KaleChips deployment. ☐ Deploy KaleChips update.
2024-01-31 The morning's Weird Side Project is a little two-step archiver for these plan files (WHY AM I LIKE THIS?). First, watch for periodic changes and save each version; then, build a web page aroudn those. For today, the "web page" might just be some "pre" tags. (Ugh, I'm going to have to html-escape things, aren't I?) Then another round of wiki cleanup before announcing the Plan 9 Foundation's GSoC application. (Hey look, sneak peak on finger!) Still waiting on client approval before pushing my last round of changes for them; hopefully this evening.