@jpasski @cynicalsecurity Yeah, making a mental note to avoid 25.0-RELEASE too 😁😁😁😁

@jperkin NM, Jonathan, ghostty looks interesting, thanks for the recommendation, and I’m interested in the long-term road test

@jperkin Any chance of getting it moved from wip into pkgsrc before the 2026Q1 branch, please? 🙏😎#pkgsrc #prettyplease 😁

@wezm Interesting - the pkgsrc metdata files (DESCR, PLIST) are still in the pkg/ subdirectory, before they were moved to the main directory. Takes me back 👍 Thanks for the memories, and sorry to hear about the PC’s memory

@sborrill Wanna get a band together?

@Nerdfest @codinghorror I took a different approach when I retired, and informed LinkedIn that the place I now worked was called “NULL”. A few years later, I was surprised to receive some email through LinkedIn from a financial consultant, offering me some financial advice, and explaining that they’d “worked with a number of your colleagues at NULL”. 🤷 🤦

@rhialto @rohare I had a quick look at this, and I think it can be fixed by converting all the "=+" increments to "+=" in both em1.c and em2.c. (Works for me, just checking that that is indeed the fix now.) Searching with a decent engine tells me that the =+ form was a holdover from B, deprecated in 1976, as it's prone to errors in parsing (i.e. is that i = +4 or i += 4). There's more in DMR's paper on the evolution of C (page 5) at https://www.nokia.com/bell-labs/about/dennis-m-ritchie/chist.pdf

@rohare @rhialto I must apologize - looking at repo history, I see I added the source code from freeshell to pkgsrc in 2013 - it's 1995-era C, and includes open-coded regexp and stdio functions, ...but the stuff I've been talking are my own efforts to bring to more recent C, which I don't see committed anywhere in pkgsrc or NetBSD. Rhialto's sources are different again, being 1 file, and with further modifications. I'll look around for the version I had. Once again, apologies