[xmonad] Re: Issue 197 in xmonad: Blocking on nextEvent stops other threads from running

[codesite-noreply at google.com]

Comment #5 on issue 197 by amdragon: Blocking on nextEvent stops other  
threads from running
http://code.google.com/p/xmonad/issues/detail?id=197

I would love to see this addressed.  In order to do simple things in the  
background
like updating the clock in my dzen, I broke down and forked completely  
separate xmonad
processes and used pipes to coordinate.  A very 90's solution that is  
downright
nightmarish next to the power and simplicity of concurrent Haskell.  Is  
there a good
reason not to simply add -threaded to xmonad.cabal?

--
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