
Hi, I'm playing with different configurations and Layouts in xmonad but it is very slow to close session in order to see how changes look like. Is there any way to test xmonad configuration more straightforwardly? Perhaps using xvnc and exporting xmonad's DISPLAY to it? How do you do it when developing?

Can't you just hit mod+q, or whatever key you've got bound to restart
xmonad? You definitely should not need to stop your entire session.
xmonad can restart itself, preserving all its state, faster than you
can blink (...plus the time it takes to recompile xmonad.hs, of course).
~d
Quoting Toni Cebrián
Hi,
I'm playing with different configurations and Layouts in xmonad but it is very slow to close session in order to see how changes look like. Is there any way to test xmonad configuration more straightforwardly? Perhaps using xvnc and exporting xmonad's DISPLAY to it?
How do you do it when developing?

Ohh I didn't know this combination I was always doing mod+shift+q Thanks a lot. El , wagnerdm@seas.upenn.edu escribió:
Can't you just hit mod+q, or whatever key you've got bound to restart xmonad? You definitely should not need to stop your entire session. xmonad can restart itself, preserving all its state, faster than you can blink (...plus the time it takes to recompile xmonad.hs, of course).
~d
Quoting Toni Cebrián ancechu@gmail.com>:
Hi,
I'm playing with different configurations and Layouts in xmonad but it is
very slow to close session in order to see how changes look like. Is there
any way to test xmonad configuration more straightforwardly? Perhaps using
xvnc and exporting xmonad's DISPLAY to it?
How do you do it when developing?
_______________________________________________
xmonad mailing list
xmonad@haskell.org
participants (3)
-
ancechu@gmail.com
-
Toni Cebrián
-
wagnerdm@seas.upenn.edu