Randomly — I mean, it can not do it for weeks but then it will start doing it randomly for hours or days — any sound played through one of the two headphones I use will be ruined by crackling noise. Of course, it it only happens with the headphones I prefer to use when I listen to music, the one that uses a standard wired/jack connector.

Nano can be configured. That shouldn’t have come as a surprise but it surprised me nonetheless. I mean, I often use nano but never cared much about it: I only use it to do quick edits in a config file or stuff like that, when I don’t want to wait for a more heavy text editor to start — nano is fast and, well, it’s always there.

Speaking of “fresh”, we should avoid thinking of packages in terms of groceries. That is a pernicious metaphor. Programs remain relevant for as long as they work and receive security fixes (where appropriate). The criterion for evaluating a program is not its recency or the hype around it, but its serviceability.

I just installed a USB speaker that lsusb identifies as a GEMBIRD Honk HK-5002 USB Speaker. It’s plug-and-play, and it works — not a great sound quality for music, but this is not what I want to use it for — save that the sound is either too loud (crackling and distorted) or, as soon as I try to lower the volume, it is muted.

When you are doing research on org-mode for notes taking in the middle of a sleepless night, to accidentaly realize, reading someone else commenting on Linuxfr.org, you had forgotten everything about your true first encounter with Org-Mode, dating back… 2011. Beside my failing memory, what strikes me the most reading this short note, is the reason I was as enthusiastic as I was hesitant to fully commit to Org-Mode back then is the exact same reason I am still hesitant and enthusiastic today, after my recent rediscovery of Org-Mode:

Many Markdown text editors under macOS or iOS come with a neat feature that lets you set the caret at a fixed position on screen, most often in the middle of the screen. This feature tries to emulate the way old mechanical typewriters used to work — it was the sheet of paper that was moving up or down, not the caret.

Why bother?

du is the usual command to show disk usage in a terminal, printing a list of all files and folders and subfolders the folder you ran it in contains. A barely readable list — to my noob’s eyes at least. ncdu (NCurses Disk Usage) turns it into something much more useful, imo, putting forward the biggest folders first in a simplified way: