From db6a72259f627ccc7d656002c79d9420be7dfc3a Mon Sep 17 00:00:00 2001
From: okan
Date: Fri, 25 Oct 2013 19:46:16 +0000
Subject: A client_delete should behave differently depending on whether the
 triggering event was unmap (with pending destroy) log destroy; we only need
 to grab/ungrab the server lock, set WithdrawnState and XRemoveFromSaveSet
 clients coming from an unmap event - doing so for clients coming from destroy
 are already gone, hence we generate errors.

---
 calmwm.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'calmwm.h')

diff --git a/calmwm.h b/calmwm.h
index 4bcd0fc..226c307 100644
--- a/calmwm.h
+++ b/calmwm.h
@@ -15,7 +15,7 @@
  * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
  * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  *
- * $OpenBSD: calmwm.h,v 1.223 2013/10/20 01:55:32 okan Exp $
+ * $OpenBSD: calmwm.h,v 1.224 2013/10/25 19:46:16 okan Exp $
  */
 
 #ifndef _CALMWM_H_
@@ -373,7 +373,7 @@ struct client_ctx	*client_current(void);
 void			 client_cycle(struct screen_ctx *, int);
 void			 client_cycle_leave(struct screen_ctx *,
 			     struct client_ctx *);
-void			 client_delete(struct client_ctx *);
+void			 client_delete(struct client_ctx *, int);
 void			 client_draw_border(struct client_ctx *);
 struct client_ctx	*client_find(Window);
 void			 client_freeze(struct client_ctx *);
-- 
cgit v1.2.3-2-gb3c3