
22 Nov
2012
22 Nov
'12
1:17 p.m.
Brandon Allbery
It occurs to me that this may be the usual $PATH issue: $PATH is set in terminals, so you can find xmobar easily, but the $PATH passed to xmonad itself is /bin:/usr/bin:/usr/local/bin or whatever your system uses as a default $PATH and xmobar installed via cabal or (some ways) git won't be found.
The easiest way to blame/discount this is to find out what PATH xmonad is getting. You can check what this is for a running xmonad by digging around in /proc. If the pid of your xmonad process is <xyz>, then: $ strings /proc/<xyz>/environ | grep '^PATH'