about summary refs log tree commit diff
path: root/calmwm.h
diff options
context:
space:
mode:
authorokan <okan>2013-10-25 19:46:16 +0000
committerokan <okan>2013-10-25 19:46:16 +0000
commit6e17b41f566865629d3dd35a6a60e081e6e2b089 (patch)
tree936ef98f0d1f8a5c6293e010a40fc9059c24ab4e /calmwm.h
parent6867821abefd761a840befcfee5a1f1f2fef9831 (diff)
downloadcwm-6e17b41f566865629d3dd35a6a60e081e6e2b089.tar.gz
cwm-6e17b41f566865629d3dd35a6a60e081e6e2b089.tar.xz
cwm-6e17b41f566865629d3dd35a6a60e081e6e2b089.zip
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.
Diffstat (limited to 'calmwm.h')
-rw-r--r--calmwm.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/calmwm.h b/calmwm.h
index 5a827b4..4f20a81 100644
--- a/calmwm.h
+++ b/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 *);