From 6e17b41f566865629d3dd35a6a60e081e6e2b089 Mon Sep 17 00:00:00 2001
From: okan <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.

---
 xevents.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'xevents.c')

diff --git a/xevents.c b/xevents.c
index 4b6ad60..e6247ab 100644
--- a/xevents.c
+++ b/xevents.c
@@ -113,7 +113,7 @@ xev_handle_unmapnotify(XEvent *ee)
 		 */
 		if (XCheckTypedWindowEvent(X_Dpy, cc->win,
 		    DestroyNotify, &ev) || e->send_event != 0) {
-			client_delete(cc);
+			client_delete(cc, 1);
 		} else
 			client_hide(cc);
 	}
@@ -127,7 +127,7 @@ xev_handle_destroynotify(XEvent *ee)
 	struct client_ctx	*cc;
 
 	if ((cc = client_find(e->window)) != NULL)
-		client_delete(cc);
+		client_delete(cc, 0);
 }
 
 static void
-- 
cgit 1.4.1