For using xmonad for developing I have add some improvements to the function `getXMonadDir'. With that patch you can select the working-directory from where xmonad reads its configuration file (xmonad.hs). It reads the environment variable XMONAD_WORKING_DIR_NAME and if it is set the working-directory ist set to this directory name. If it is not set it works as before that means the working directory is $HOME/.xmonad. An example of using the environment variable: $ export XMONAD_WORKING_DIR_NAME=xmonad-test && xmonad means that xmonad try to start xmonad with the configuration file in the directory $HOME/.xmonad-test -> $HOME/.xmonad-test/xmonad.hs is the configuration file. In my case I start Xephyr with $ Xephyr :1 and after that I start xmonad with a different working directory $ DISPLAY=:1 && export XMONAD_WORKING_DIR_NAME=xmonad-test && xmonad br \= odi -- Oliver Dunkl WEB: http://github.com/odi IM: odi@jabber.ccc.de IRC: odi(irc.freenode.net)
On Wednesday, October 15, 2014 04:55:42 PM Oliver Dunkl wrote:
For using xmonad for developing I have add some improvements to the function `getXMonadDir'. With that patch you can select the working-directory from where xmonad reads its configuration file (xmonad.hs).
Maybe you'd also like to have a look at https://code.google.com/p/xmonad/issues/detail?id=484 It would be very nice if such a great software like xmonad would not clutter my homedir.
participants (2)
-
Oliver Dunkl -
Thomas Koch