Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!mit-eddie!uw-beaver!tektronix!orca!tekecs!bobtl
From: bobtl@tekecs.TEK.COM (Bob Toole)
Newsgroups: comp.windows.x
Subject: Re: Killing X-windows
Message-ID: <9035@tekecs.TEK.COM>
Date: Thu, 20-Aug-87 15:30:59 EDT
Article-I.D.: tekecs.9035
Posted: Thu Aug 20 15:30:59 1987
Date-Received: Sat, 22-Aug-87 16:15:54 EDT
References: <556428318.rfb@h.gp.cs.cmu.edu>
Reply-To: bobtl@tekecs.UUCP (Bob Toole)
Distribution: world
Organization: Tektronix, Inc., Wilsonville, OR
Lines: 13

As previously mentioned, it is very easy to write a program that
will destroy a window.  I have written such a program and find it
less than satisfactory, because it destroys the window but does
nothing for the client using that window.

The best result I get is that the client dies when it next tries
to use the window.  This usually leaves garbage diagnostics printed somewhere.
The nastier result is that a program is hung waiting for input
that it will never get.

Anybody have ideas on how to tell the client "I just zapped your window"?
And please don't tell me to wait for X11.  I know X11 is wonderful,
but that doesn't help now.