When I press the key combo to restart xmonad, it is currently failing,
displaying a xmessage that it's not in PATH. Strace shows:
22164 execve("/bin/sh", ["/bin/sh", "-c", "if type xmonad; then xmonad --re"...], [/* 58 vars */]) = 0
22164 write(1, "xmonad is /usr/bin/xmonad\n", 26) = -1 EIO (Input/output error)
22164 write(2, "sh: ", 4) = -1 EIO (Input/output error)
22164 write(2, "type: I/O error", 15) = -1 EIO (Input/output error)
22164 write(2, "\n", 1) = -1 EIO (Input/output error)
This apparently has something to do with the way I started xmonad this time,
which I think involved xmonad -replace run inside a terminal, which was then
backgrounded, disowned, and the terminal closed.
lrwx------ 1 joey joey 64 Aug 13 13:56 0 -> /dev/pts/1\ (deleted)
lrwx------ 1 joey joey 64 Aug 13 13:56 1 -> /dev/pts/1\ (deleted)
lrwx------ 1 joey joey 64 Aug 13 13:56 2 -> /dev/pts/1\ (deleted)
lrwx------ 1 joey joey 64 Aug 13 13:56 3 -> socket:[16313]
I think this could probably be avoided by redirecting stdout and stderr to
/dev/null when running the "type" command.