I don't really have much to say. I mean, what is there to say? I wake up at 0500hrs in the morning, spend some time with God, catch up on the news over the RSS feed, do the short set of exercises from The Hacker's Diet to maintain my muscle mass, take a cold shower, brush my teeth, chug a cup of weak instant coffee to take my antihistamine, head into my room to check out other news sources online (hello /., and Reddit), start getting dressed by 0610hrs, leave the apartment by 0625hrs, take the bus between 0630hrs to 0645hrs (napping for the first 20 min and then proceeding with reading), change to the next bus at around 0730hrs to 0745hrs (mostly reading), alight at the bus stop between 0800hrs to 0810hrs, march up the hill and set up my work laptop between 0810hrs to 0825hrs while making my next mug of coffee, work till 1130hrs, hide somewhere far from my work space for one hour (spent mostly reading, unless I feel knackered, in which case I'd begin with a short nap of 15 min), make my last mug of coffee before continuing my next bout of work till 1750hrs, do my daily document back up, lock away everything except the LAN cable and monitor into the puny pedestal drawer, leave by 1815hrs, hop on the bus en route to Harbourfront (reading all the way), decide to have dinner there or otherwise, and eventually make my way home by 2030hrs, shower, chill in front of Eileen-II either reading or doing something in Minecraft or write some program or write something else (like a blog entry) or catching up on more news while simultaneously watching/listening to Hololive archives at speeds between 2.0× to 3.0× depending on the streamer and content, grab my other antihistamine and a multivitamin pill by 2330hrs, set up my mattress on the floor, set my alarm to 0500hrs the next day (0515hrs on the device, because I purposely run it 15 min faster than real-time), spend some time with God while in seiza, do my squats, do my hamstring and adductor stretches, do my crunches, then crash out by 0000hrs.
That is literally my typical day. There is hardly time for anything or anyone else.
Is this living? I don't know... what is living for a middle-aged Asian man in Singapore with a middle-of-the-line income like me anyway?
🤷♂️
If you know the answer, do write a comment and let me know. Because I really don't know.
------
SumatraPDF recently updated to v3.4.1 (as at writing). While it supposed to have improved features from the updated components, I do not recommend its widespread use just yet. There are two deal-breakers for me that preclude its use:
- The F12 key to show the bookmark side panel has bad focus after, which means that after showing the bookmark side panel, one can no longer press F12 to toggle the side panel away again. As noted in the link, it will be addressed in the next release, either v3.4.2, or the pre-release of v3.5.
- The removal of FontName and FontSize options (compare the help file on settings for v3.3.1 against the one for v3.4.1). It's a deal breaker because the default font for Ebooks (that I can't seem to change/patch directly) is Georgia, while my preferred reading font these days is Atkinson Hyperlegible just for the much better readability. I'm not a fan of the E-book format (i.e. Mobi or EPUB) that isn't PDF anyway, but the SCP Foundation tomes are necessarily in those formats due to the sheer size and unwieldiness otherwise. Reading these 3k+ pages with Georgia instead of Atkinson Hyperlegible is eye-strain city, and is a hard-pass from me.
In other news, Frescobaldi finally released a Windows build for v3.2, some 22 days after the Linux builds were released.
``MT, I thought you worked with Linux? What's with the Windows daddy-o?''
Linux is for work stuff---for not-work stuff, I use a mix of Windows+Cygwin to get things done, with a side of Linux command-line from a VM when there is absolutely no other [easy] way of doing it.
That said though, Frescobaldi in the new 22.04 LTS release of Ubuntu is broken for the same reason why v3.2 exists---Frescobaldi v3.1.3 cannot run with the Python 3.10 interpreter due to some increased strictness involving types (see Issue #1433 for an example of the class of errors). I'm not sure when the package maintainer will fix this, but that also slows/stops me from setting up a 22.04 update on machines under my control.
Anyway, that's it. It's 2315hrs as I write this sentence, and I'm just going to push this out and call it a night.
Till the next update, whenever it might be.
No comments:
Post a Comment