[xmonad] kill -STOP/-CONT hack

[Adam Sjøgren]

Brandon writes:

> I was waiting to see if the author of the contrib would jump in, but I
> guess not. (Contribs are contributed, as the name suggests, and we can't
> necessarily support all of them directly.)

That is, of course, fair. It is ok to discuss contrib stuff on this
mailing list, though, right?

> That said, browsers are likely to be a specific screw case these days
> because sandboxing means that windows or even individual tabs may be
> running in their own processes (they certainly are in Chrome / chromium).

Ok, let's take out the complexity that is webbrowsers and try something
simpler.

If I start another program, say xeyes, on workspace 1, its state is
reported by "ps faux" as 'S', and eyes are following my mouse pointer.

If I then "killall -STOP xeyes", the eyes stop moving, and the state is
reported as 'T' by ps.

When I "killall -CONT xeyes", the eyes move again, and the state is back
to 'S'.

If I move xeyes to workspace 3, the state keeps being reported as 'S' by
ps. It never changes to 'T', even 15 seconds after switching to
workspace 1.

This makes me think that something might not be working in my setup.

This is with:

       , layoutHook = avoidStruts $ modWorkspace "3" stoppable $ layoutHook defaultConfig

in my xmonad.hs.

Have I misunderstood what is supposed to happen?


  Best regards,

    Adam

-- 
 "Sunday morning when the rain begins to fall                 Adam Sjøgren
  I believe I have seen the end of it all"               asjo at koldfront.dk