[comp.windows.x] xkill and awm don't get along

corbet@mead.ucar.edu (12/03/88)

I tried to use xkill to get rid of a window on my display...the result is
that my window manager (awm) died instead.  The results were somewhat
disorienting, as all of my icons exploded and general chaos ensued.

Since then, I have done some playing, and I have come to the following
tentative conclusion: since awm reparents windows to put things like title
bars on them, xkill is always seeing a window owned by awm when it goes about
its grim business.  So, awm always gets nailed.

It's hard to see a way around this problem, especially with my novice-level 
knowledge of X programming.  But I thought I would pass it on...

Jonathan Corbet
National Center for Atmospheric Research, Field Observing Facility
corbet@stout.ucar.edu

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (12/04/88)

    I tried to use xkill to get rid of a window on my display...the result is
    that my window manager (awm) died instead.

xkill is broken.  It needs to use the (still under development)
conventions for walking down the tree to find the "real" client window.
xkill was probably only ever tested with uwm ...

spencer@spline.eecs.umich.edu (Spencer W. Thomas) (12/06/88)

I might point out that awm has an "f.destroy" action that works
perfectly well.

=Spencer (spencer@crim.eecs.umich.edu)