Re: [xmonad] Issue 350 in xmonad: Investigate using Dyre for xmonad configuration

Updates: Cc: vogt.adam Comment #10 on issue 350 by vogt.a...@gmail.com: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 Changing to dyre will also addresses the rare event that xmonad tries to pass an excessively long string to the new process that replaces it, since if I recall correctly, dyre seems to save the state in '/tmp' (at least by default, which should probably be changed to ~/.xmonad/state or so). The error is the first point below, and today in #xmonad pielgrzym ran into it too. http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Actions-WorkspaceCursors...