On Mon, 07 May 2012 02:06:31 -0400 wagnerdm@seas.upenn.edu wrote:
There have been various times when I've wished I could just spawn a thread in xmonad. Just recently, for example, it was pointed out to me that the default mod+q binding starts a brand new process just to keep xmonad responsive while it recompiles the configuration file. This is silly.
Why is it silly? It's not like the overhead of starting a new process is going to be anything but noise compared to recompiling the configuration file.
Here is a patch bundle that makes xmonad ask X to be thread-safe, and rewrites the default mod+q binding to take advantage of the new thread safety.
What's the performance hit from making X thread-safe?
For that matter, if you are using Haskell threads instead of OS
threads, do you need to make X thread safe? [Sorry if this is a silly
question - I'm not really familiar with using Haskell threads.]