brandon s allbery kf8nh

But there are distros which package xmonad with a session file of its own. This said, that's kinda their problem since they also should ship `/usr/bin/xmonad`. But users installing directly...

`~/.xsession` is the standard name for a session startup file, cross-platform. I think only Fedora changes this, and even then you can still use the standard name; they just prefer...

As I mentioned, environment variables (such as `$HOME`) do not work in session files. That is why the one I linked to earlier says `/home/allbery` instead of `$HOME`.

Worth noting here is that session files are generally read by the display manager at its startup, so per-user things are not available (hence no environment variables and only the...

That is however the traditional way of doing things. There's also the RHEL/Fedora trick of having a session which copies `/etc/X11/Xsession` but reads `~/.Xclients` and then runs a particular window...

It does, but you can't put that in a cabal or stack package. OS distributions, on the other hand, can.

Irrelevant. The message about recompiling is output any time you start xmonad via the standard executable and have your own config; the actual recompilation check is done afterward. On Sat,...

The issue here is that bindir/xmonad always checks for a user config with intent to rebuild it if necessary before transferring control to it. So if you run xmonad in...

`unGrab` should really be merged to either `XMonad.Core` or `XMonad.Operations`. But yes, if nothing else this should be a FAQ.

How is your ghc installed? (I presume ghcup, but I know sid is currently upgrading its ghc and dependencies and is currently, well, unstable.) This error usually indicates an incompatible...