search

vicfryzel / xmonad-config

My xmonad and xmobar configuration, plus necessary scripts to make things more usable.
http://www.vicfryzel.com/2010/06/27/obtaining-a-beautiful-usable-xmonad-configuration
MIT License
464 stars 161 forks source link

Xmobar fixes #7

Closed floer32 closed 11 years ago

floer32 commented 11 years ago

Changes to README, and to one line in xmobar.hs. Changes made in order to make xmobar install properly in more environments (the author is using Arch -via- Manjaro Linux 0.83 XFCE Edition). These changes primarily address Issue #6.

vicfryzel commented 11 years ago

I need to better understand why you are not using xmobar from the community branch in Arch. The change you make to xmonad.hs breaks users on Ubuntu, for instance, because the explicit path of xmobar changes to /usr/local in the case of installing it from cabal. I can't seem to reproduce your issue on #6.

floer32 commented 11 years ago

Hmm. The reason I was using it installed via cabal is because I just couldn't get it to work when I was installing from AUR - like no signs of life. I fiddled with things the same way - like installing dmenu-path-c, switching it out with dmenu_run, etc. But they didn't work. Then I tried installing it via cabal, and fiddling around, and it started working. I usually prefer PyPI to general-use repositories with Python packages, so I guess I wasn't thinking of installing from cabal as being subsidiary to installing from AUR. In any case, I'm new to Arch, so this is probably all moot.

Breaking the path for Ubuntu users is pretty bad, I didn't realize I was doing that. Maybe these aren't good changes for everyone else after all!