Suraj N. Kurapati

@cdlm the patch is here: notEvil/clever-f.vim@15af064ac967a784614b6a0931188798efcd715b :crossed_flags:

`xprop` emits a `WM_COMMAND(STRING)` line that contains the $0 and ARGV used to launch the client. Unfortunately this line only appears for some clients, such as terminal emulators.

A simpler sub-problem is to preserve the arrangement of clients on a view. Once we know how to do this, the next step is to (1) spawn or (2) watch...

No, I have not returned to this issue since the last update. I keep my system on all the time, or hibernate it when it needs to power off, so...

Saving and loading the arrangement of clients is certainly possible at present (see http://github.com/sunaku/wmiirc/issues#issue/3/comment/183096). The challenge is figuring out how to bring those clients into existence from scratch (see http://github.com/sunaku/wmiirc/issues#issue/3/comment/76986)....

@ctx - Your approach seems interesting but I don't yet understand how the three requirements you mentioned would be used to implement session support. Could you post your bash prototype...

Good idea. We could try using Ruby 1.9 fibers with a global queue. Each fiber would yield to the next one by: ``` queue.enq current_fiber next_fiber = queue.deq next_fiber.resume ```...

@nougad I just re-read this issue report and, at the end, it sounds like you already implemented this idea. Is that true?

The main cause of [power-inefficiencies in Ruby 1.9](http://redmine.ruby-lang.org/issues/3919) was [a timer-thread issue](http://redmine.ruby-lang.org/issues/3436). It has since been fixed, so perhaps your battery lasts longer now?

Interesting, I will need to study my powertop output more closely. I was only looking at the number of wakeups because that was the initial problem ruby < 193 had....