[xmonad] bringing xmonad into the threaded world
mwm at mired.org
Mon May 7 11:29:50 CEST 2012
On Mon, 07 May 2012 02:06:31 -0400
wagnerdm at 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
> 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
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.]
Mike Meyer <mwm at mired.org> http://www.mired.org/
Independent Software developer/SCM consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
More information about the xmonad