[xmonad] kill -STOP/-CONT hack

[Brandon Allbery]

On Tue, Jun 14, 2016 at 6:11 PM, Adam Sjøgren <asjo at koldfront.dk> wrote:

> Brandon writes:
> > On Tue, Jun 14, 2016 at 5:52 PM, Adam Sjøgren <asjo at koldfront.dk> wrote:
>
> >> 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.
>
> > Wait, are you ever making workspace 3 current in this, or just moving
> with
> > mod-shift-3? Layouts don't (and can't) react to the latter; the layout
> can
> > only stop and start processes when you switch to or away from a
> workspace.
>
> Makes no difference either way. Does it work for you?


Haven't tried because I don't have a sandbox setup on this machine (to run
a separate xmonad setup from my main one in xephyr).

I just realized xeyes was a bad choice; Stoppable relies on _NET_WM_PID,
and...

pyanfar «.xmonad*pyanfar» Z$ xeyes & sleep 3; xprop -name xeyes
_NET_WM_PID; kill $!
[1] 14711
_NET_WM_PID:  not found.


-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/xmonad/attachments/20160614/70885a50/attachment.html>