Comment #3 on issue 350 by vogt.adam: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 I can't find a version of dyre on hackage that supports base-3, so somebody either needs to fix dyre in that respect, or we should accept the loss of ghc-6.8 compatiblity (this is particularily a concern if we want to minimize trouble for ubuntu users, which still have ghc-6.8). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Comment #5 on issue 350 by vogt.adam: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 I have a branch which uses dyre: http://code.haskell.org/~aavogt/xmonad-dyre Compatibility for changes to the type of recompile (which could be left as-is, but the type should suggest what is legal): http://code.haskell.org/~aavogt/XMonadContrib/dyre/ And minor changes that were necessary to dyre (though more need to be made to duplicate xmonad's current behavior, especially with respect to recompilation checking for ~/.xmonad/lib): http://code.haskell.org/~aavogt/dyre.git

Comment #7 on issue 350 by vogt.adam: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 I have not heard either way. That being said, my changes aren't complete and I was more or less asking for help in this (dated Nov 1, 2010): The following darcs repository xmonad uses dyre: http://code.haskell.org/~aavogt/xmonad-dyre/ I'm using ghc-6.12.3 and some part of the recompile seems to die: If I touch ~/.xmonad/xmonad.hs, then (xmonad --restart, or use a keybind to restart (Right True)) the WM exits due to this exception: Configuration '/home/aavogt/.xmonad/xmonad.hs' changed. Recompiling. xmonad: waitForProcess: does not exist (No child processes) The recompile dies with the same exception here, but the result is correct: touch ~/.xmonad/xmonad.hs; xmonad --recompile; xmonad --restart Some feature requests, somewhat related to what's already done in xmonad. (see http://code.google.com/p/xmonad/issues/detail?id=350) 1. there should be a way bypass dyre's recompilation checking; and force that executable to exit once recompilation is done. For the latter I've tried unsuccessfully: - write a global IORef before using dyre, and read it in the realMain which I'm not sure why that doesn't work - set config parameters, which obviously doesn't work since the config in ~/.xmonad/xmonad.hs shouldn't ask for early exit 2. dyre's recompilation checking could look in ./lib given -ilib, which makes changing files in a modular config trigger a recompile Thanks for you help, Adam

Comment #9 on issue 350 by vogt.adam: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 This may or may not belong to dyre's responsibility, but it would be nice to specify that the xmonad.hs is compiled using the correct -package. If Cabal permits, ghc's package names could include those hashes, so multiple xmonad-0.9.2 could coexist (ex. global and user). Confusion resulting from unexpected results from multiple xmonad installs happens often in #xmonad. After a compile failure with restricted package versions fails, a second attempt should be made without the -hide-all-packages. That way multiple versions of xmonad could coexist for a single user, and it may make install errors clearer. The only downside I see is excessive code complexity. Haskell is more consise than my current description and some parts may be in dyre, so it might be worthwhile.

Comment #11 on issue 350 by vogt.a...@gmail.com: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 Issue 501 has been merged into this issue.

Updates: Cc: woozlet...@gmail.com Comment #13 on issue 350 by allber...@gmail.com: Investigate using Dyre for xmonad configuration https://code.google.com/p/xmonad/issues/detail?id=350 The "temporarily disable SIGCHLD ignoring" code in recompile (uninstallSignalHandlers, installSignalHandlers) is *not* optional; the error you are getting is a symptom of not disabling it before rebuilding. You will need to find some way to integrate that with Dyre. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

this is particularily a concern if we want to minimize trouble for ubuntu users, which still have ghc-6.8

As of Ubuntu 9.10, which was released october 29th, this is no longer true.