Well, okay, there are plenty of modules in contrib that I would never use (and for that matter, several things in core I disable or ignore). As long as:

1. The code is clean.

2. It won't segfault.

3. It's gotchas are well-documented.

Then I'm happy with it. From a quick glance, it appears so. The advice in $usage to do `layoutHook def ||| stoppable (layoutHook def)` (thereby doubling your list of layouts?) seems a bit weird, but maybe I'm misunderstanding it. Applied.

On Fri, Sep 26, 2014 at 7:57 PM, Brandon Allbery <allbery.b@gmail.com> wrote:

On Fri, Sep 26, 2014 at 10:53 PM, Devin Mullins <devin.mullins@gmail.com> wrote:
Brandon/Paul - ok to submit? I haven't reviewed this code, but I'll take your words on it.

On some level I kinda dislike the whole idea, but (a) I can certainly see its usefulness, and (b) as long as users are aware of the caveats involved (cut and paste was mentioned; also note that anything that is holding open a network connection will probably catch an RST on resume if suspended for too long) it's up to them whether to use it or not.

--
brandon s allbery kf8nh sine nomine associates
allbery.b@gmail.com ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net