I am trying to get xmobar running on GNOME3. However, xmonad starts the process, then it quits. I am not sure why, but I know that it quits because I changed the output handler (ppOutput) to first use writeFile then to the xmobar Handle. I saw the contents that would have been piped to xmobar in the file. If I start xmobar manually after xmonad has started, it starts fine, reading "Updating..." awaiting input. I have minimised ~/.xmonad/xmonad.hs and I have tried many variants to try to resolve the issue: https://gist.github.com/4129597 I have also tried fiddling with ~/.xmobarrc but this is how it currently stands: https://gist.github.com/4129924 Any tips are immensely appreciated, because I have run out of ideas! -- Tony Morris http://tmorris.net/
On Thu, Nov 22, 2012 at 3:07 AM, Tony Morris
I am trying to get xmobar running on GNOME3. However, xmonad starts the process, then it quits. I am not sure why, but I know that it quits because I changed the output handler (ppOutput) to first use writeFile then to the xmobar Handle. I saw the contents that would have been piped to xmobar in the file.
If I start xmobar manually after xmonad has started, it starts fine,
Do you ever see the xmobar appear? 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. This would show up as errors in ~/.xsession-errors on many, but not all, systems. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix/linux, openafs, kerberos, infrastructure http://sinenomine.net
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'
On Thu, Nov 22, 2012 at 08:07:57 GMT, Tony Morris wrote:
I am trying to get xmobar running on GNOME3. However, xmonad starts the process, then it quits. I am not sure why, but I know that it quits because I changed the output handler (ppOutput) to first use writeFile then to the xmobar Handle. I saw the contents that would have been piped to xmobar in the file.
If I start xmobar manually after xmonad has started, it starts fine, reading "Updating..." awaiting input. I have minimised ~/.xmonad/xmonad.hs and I have tried many variants to try to resolve the issue:
https://gist.github.com/4129597
I have also tried fiddling with ~/.xmobarrc but this is how it currently stands:
https://gist.github.com/4129924
Any tips are immensely appreciated, because I have run out of ideas!
I use xmonadpropwrite which is what xmonad starts. I've found that it's much more reliable at starting properly (xmobar doesn't start properly and consistently without a shell wrapper I have). Since xmobar itself isn't on the XMonad pipe anymore, I can update my configuration, restart it, or whatever without having to restart XMonad to get the pipes hooked up again. -- Ben
participants (4)
-
Ben Boeckel -
Brandon Allbery -
Justin Bogner -
Tony Morris