We are at a point where a 20mhz accelerator from ~1997 for a niche computer with almost no software is knocking on the door of an Apple Vision Pro. Take that.
Released v0.6.1 just fixing one stupid little regression from refactoring: The terminfo writer must never be used when output does not go to stdout 🙈
So far so good, I just thought there was yet another bug, testing redirected output on #Windows. I always got a file encoded as #UTF16LE, no matter which format I chose (and with #UTF8 chosen, the output was just broken). Meditated on the code for a while. Looks all perfectly good.
Finally, I tested in good old #CMD. And it worked perfectly well.
So, #Powershell is messing with the encoding of my stdout stream on redirects. Really? Really??? WTF, #Microsoft? How should that ever do any good? 🤯
? I have mystery power ons for my desktop that aren't recorded in it, and my laptop was hot after being at home, plugged in and closed ALL day so it apparently woke. But no wakes recorded.
Anyone have experience setting up a #rdp solution with an elderly parent when you can't be physically present to assist on the config for their end? The ISPs must do this all the time.
I'm on Linix, they're on windows. I've read #chrome has a screen share option, wonder if that'd be a jumping off point for #cmd or #powershell access. All I need is a shell...
Would love more stories of things that helped you in the last ~5 years!
(as usual, no need to reply if you don’t remember, or if you’ve been using the command line comfortably for 15 years — this question isn’t for you :) )