On Mon, Jan 13, 2014 at 2:07 AM, Erik de Castro Lopo
It's a very bad idea without rearchitecting xmonad's main loop to allow it to support anything other than X11 events. In particular, you really want timed events for a status bar, and at present the only way to get that while maintaining access to xmonad's internal state is to have a separate thread periodically sendMessage X11 events to the main thread.
Taffybar already runs happily in its own process without access to xmonad's internal state, so all it would be doing is using the exising communication protocols and sharing the RTS.
As already noted, Xlib isn't reentrant so this would not work anyway, even if you gave the taffybar thread its own server connection (which would be necessary in any case). There *is* a function that enables Xlib use in a threaded environment, but it works by effectively wrapping all Xlib calls in a big mutex so performance pretty well tanks. In short, it's not worth it. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net