ttj - Tom Jones

The reason I haven't used my preferred window manager on my laptop for the last 20 years is that as soon as you choose a different window manager, all sorts of laptoppy things stop working.  Like closing the lid and having it suspend. There is obviously no reason this should be so, other than poor software design.  But the behaviour has been basically the same on all linux for decades and decades. I've just checked with fvwm on Debian 12, which is current.  I put my fvwm config there, log in, it's running.  I close the lid.  The red light on the X1 nano gen 2 is pulsing, indicating the laptop is asleep.  Maybe it's actually worked!  I open the  lid.  The screen is already on, too quick, must have been on the whole time.  So why was the indicator light indicating it was suspended? It brings back memories of overheating laptops in briefcases, where I thought it had suspended, and it hadn't.  I have been exactly here before. It's silly...

In the spirit of visual peace, cursors should not blink. Stopping the cursor blinking for the gnome terminal is obscure.  You have to click on the lines to get a menu, then choose preferences.  But instead of being somewhere sensible, the blinking is in a section called "Unnamed".  Because some devtard, suffering from a bad case of generalisationitis, thought: well, these setting don't just need to be set once per user, so let's have multiple ones, call them profiles.  And for some reason the actual profile in use, that 99% of people are using, ends up having a name of "Unnamed".  And it's in this profile, named "Unnamed", that the setting on the blinking of the cursor is to be found. But wait!  If you were going to change "Allow blinking text" from "Always" to something else, that's not it.  That's there to trick you.  The way to get visual peace is the other one.  Change "Cursor blinking" from "Defau...

I noticed my PC's fans whirring loudly. Running top(1), I saw that firefox was pegging the CPU.  In most cases, this is caused by a web page pegging firefox, and, more decisively, by firefox allowing itself to be pegged.   It was not possible to select different tabs in firefox windows to get an idea what was going on (per-app MDI like tabs is in any case reflection of failure to handle groups of windows at the OS / window-manager level.  Multiple app instances / documents / tabs in one big process ala firefox is itself terrible design.  Web pages / documents should not live in the same memory space and process together just because they being handled by the same app, let each tab (window / doc / web page / app instance) be its own process) Firefox was completely unresponsive.  Moving the mouse started to get glitchy.  I had to move the mouse, and then wait a few seconds.  I tried killing the window with my window manager commands "Close", "Delete...