From 349c907cbf1cba6988b971073f84a91ffdc8074d Mon Sep 17 00:00:00 2001 From: Přemysl Eric Janouch Date: Sat, 25 Mar 2023 11:08:30 +0100 Subject: X11: act on DestroyNotify rather than UnmapNotify This makes the program survive i3 restarts, which cause a sequence of: UnmapNotify, ReparentNotify, MapNotify. --- nncmpp.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/nncmpp.c b/nncmpp.c index 17c7685..e4e24cd 100644 --- a/nncmpp.c +++ b/nncmpp.c @@ -6748,7 +6748,10 @@ on_x11_event (XEvent *ev) case SelectionClear: cstr_set (&g.x11_selection, NULL); break; - case UnmapNotify: + // UnmapNotify can be received when restarting the window manager. + // Should this turn out to be unreliable (window not destroyed by WM + // upon closing), opt for the WM_DELETE_WINDOW protocol as well. + case DestroyNotify: app_quit (); break; case FocusIn: -- cgit v1.2.3-70-g09d2