Ariel Millennium Thornton @arielmt@computerfairi.es

I'm still tinkering with with my desktop icon theme.

I decided I don't need a tall xload because I'd only need to know if the load average gets above 4.0 or 5.0, not necessarily how much above.

I also decided that a wider xcal would help me reread date info a lot quicker. (I just realized I'll have to widen it more for "September.")

Combine those together, & that let me move xclock closer to the corner, too.

(Wallpaper is the left part of "Chakats at the Onsen")

Swiped from https://twitter.com/AlecMuffett/status/999616307241906176 on birdsite:

NPR has the best creative solution. (You can shortcut it by replacing "www" with "text" in the URL.) https://computerfairi.es/media/_7qtaotMWoqCRAl_vqU https://computerfairi.es/media/pgoIMpkj0wtCx3WaMEg

Double whoops on me, I forgot to add context with a non-LA Times story link: https://slate.com/technology/2018/05/the-la-times-isnt-letting-europeans-read-its-site-thanks-to-the-eus-new-internet-rules.html

Happy GDPR day, Europe! I read that it won't actually fix anything, but like shining a light under the kitchen cabinets & sending the roaches scurrying for cover, it'll reveal just how bad data mishandling has gotten.

The LA Times website is now unavailable in the EU because it isn't GDPR compliant. If I had to guess why, it would involve the unscrupulous state of web ads. Creepy personalization is my second guess. Whoopsie.

I've been so busy with work and so not sleeping well that I haven't had a chance to meaningfully do anything personal.

Specifically, who parses unescaped angle-brackets enclosing a URL as part of that while /NOT/ parsing freaking COMMAS up against that URL as part of the same URL?

Who parses unescaped angle-brackets enclosing a URL as part of the URL being enclosed?

"- also, 5 programs running in windows that look like icons"

LOL I can't count. I have 8 programs running: xcal, xload, xman, xclock, & xbiff 4 times.

On the fairyfloss tangent, I added the following X resources to my ~/.Xdefaults file to make my xterm match:

XTerm*background: #5a5475
XTerm*foreground: #f8f8f2
XTerm*cursorColor: #c2ffdf
XTerm*scrollbar.foreground: #ffb8d1
XTerm*scrollbar.background: #716799

(On some systems, the user's X resources file is ~/.Xresources or ~/.Xres instead. See manpages X(7) and xrdb(1).)

(Also also, there's a vim port, which is why I made xterm match: https://github.com/tssm/fairyfloss.vim )

... I have 66 icons to manage so far, wow. :/

- 18 icons I configured to do nothing but look pretty (by running `true` if clicked)
- 48 icons that actually do things when clicked
- also, 5 programs running in windows that look like icons

I ended up writing a shellscript to help me manage them all (so much for not being as hard as it looks), because I'm definitely not done moving them around and adding more. https://computerfairi.es/media/FPgpo1AoVETrludsk38

I am so close to liking this icon theme I'm working on well enough to call it ready to write about. Whole screen, left-edge icons, and top-edge icons.

(Wallpaper: "Chakats on the Beach" by rickgriffin https://www.furaffinity.net/view/5271044/ )

(Also, I like sailorhg's fairyfloss editor theme too much: https://sailorhg.github.io/fairyfloss/ - https://github.com/sailorhg/fairyfloss/ - and that's why I turned my xterm pastel purple, which I also need to share.)

. https://computerfairi.es/media/kZoOszITrkVFQqYQnds https://computerfairi.es/media/eBqRzkim3uTTyykgsv0 https://computerfairi.es/media/3Q-HA6O69O5sSQnk4sE

Plug a cheap bog-standard USB mouse into the PC.

Linux: It just works.
Unix: It just works.
Windows: https://computerfairi.es/media/OgwMZ2cgyNhoq-MlT-Q

That is, unless GROFF_NO_SGR is set. The only places I found it documented were on the Internet (for Linux-specific xman weirdness) and in the grotty(1) manpage.

I forgot to note why GROFF_NO_SGR needs to be set when starting xman on #FreeBSD:

During compiling, xman.c checks which OS it's being compiled on & hardwires `nroff -mandoc` as its page formatting aid if it detects the BSDs. However, nroff's mandoc macros output ANSI escape codes, while xman expects typewriter-style "back up & overstrike" codes.

Want to use xman on #FreeBSD? Start it this way to get manpages formatted right:

#!/bin/sh
export GROFF_NO_SGR=1
/usr/local/bin/xman

Before & after: https://computerfairi.es/media/4Ac1TAE-XvlGV9p_G0M https://computerfairi.es/media/9-5mWICKz0GBtbG1nXg