esa

Idunno, that might be approaching “one day of patchy electricity can change how you view computers vs mechanical typewriters”. Here people would likely use their mobile internet, especially if the company is paying their phone bill.

I’ve been using Fantasque sans mono for a bunch of years now.

I think I wouldn’t find it particularly useful, as I’m used to the quasi-programming I can do in a terminal. The shell commands take some time & effort to learn, but once you’re over that hump, being able to extract and compose information is really good. The primary shell tools I’d miss in a gui are |, jq, awk, sed and grep/rg, as well as for, if, while, variables, and having everything in one lightweight window.

The part is constructed from two parts:

1. ls: list
2. usb: usb

It lists usb devices that your machine (/kernel) knows has been connected; they may not necessarily be usable.

E.g. I have some sound output device connected via USB to one machine. On most of my machines I’ve switched from pulseaudio to pipewire¹, and I figured I’d bring that machine closer to the others so there’s less variance. Unfortunately the sound output device didn’t want to work with pipewire. The problem manifested as no sound and pipewire not listing the device. lsusb helped me know that the machine at the very least recognized the device, but wasn’t currently able to use it. (It did actually also show up as an error in dmesg -H, but reinstating pulseaudio let the device work again as normally. So now I just have to live with a situation where some machines use pipewire because _bluetooth and others use pulseaudio because … usb?¹)

¹ There’s a memory of ALSA vs OSS I didn’t want to be reminded of