brandon s allbery kf8nh

It is, it's just one of those ugly hacks that causes undue pain in the long run. :/

Also, if we are forced to do this kind of hack, I'd prefer something like ```autoFloatRule``` where we could migrate ```isDialog``` from ```ManageHelpers``` and have ```EwmhDesktops``` apply it by default....

(there's an example of cognitive cost hidden in that last comment that I almost edited out, and then decided should stay to make the point. }:> )

It'd probably be a `Query Bool` controlling whether to float or not, although instead it could be a full `ManageHook` also containing the float operation --- but that produces a...

It occurs to me that some corner cases with `killAllStatusBars` might be avoided with a proper `shutdownHook`.

A `shutdownHook` in xmonad won't help with that, since the X server will still be running when the hook is run.

There is no magical way to just nuke all child processes. Plus there are the processes that aren't direct children (consider a status bar launched from a shell for debugging,...

Moreover, if you go check the history of `X.H.StatusBar`, you will find there are problems with the whole idea of tracking applications: conceivably an application exits, xmonad doesn't know it,...

It was attempted at one point but broke xmonad for sjanssen (the original xmonad developer) because he was on OpenBSD. I don't think you can find it in repo history...

My ideal for the bespoke `shutdown` function would be to set a new flag in the `XState` (which is not generally accessed directly by users, only piecemeal via `gets`) and...