2022/12/28

2022-12-28 00:18:03 +0100sogens(~sogens@103.75.11.26)
2022-12-28 00:18:19 +0100Natch(~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) (Remote host closed the connection)
2022-12-28 00:35:17 +0100sogens(~sogens@103.75.11.26) (Quit: WeeChat 3.7.1)
2022-12-28 00:35:36 +0100sogens(~sogens@103.75.11.26)
2022-12-28 01:04:49 +0100Natch(~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se)
2022-12-28 02:04:59 +0100ft(~ft@i59F541CC.versanet.de) (Ping timeout: 264 seconds)
2022-12-28 02:27:10 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
2022-12-28 02:44:24 +0100sogens(~sogens@103.75.11.26) (Ping timeout: 272 seconds)
2022-12-28 04:04:59 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 268 seconds)
2022-12-28 04:20:43 +0100td_(~td@83.135.9.15) (Ping timeout: 260 seconds)
2022-12-28 04:22:29 +0100td_(~td@83.135.9.57)
2022-12-28 04:24:29 +0100banc(banc@gateway/vpn/protonvpn/banc)
2022-12-28 04:41:27 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::) (Quit: The Lounge - https://thelounge.chat)
2022-12-28 04:44:04 +0100terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::)
2022-12-28 05:09:29 +0100sogens(~sogens@103.75.11.26)
2022-12-28 10:08:54 +0100sogens(~sogens@103.75.11.26) (Ping timeout: 252 seconds)
2022-12-28 14:46:55 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
2022-12-28 15:36:21 +0100diep(~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c)
2022-12-28 15:39:09 +0100 <diep> Hi! What happens when "kill" is called to close/delete a window? Is a "close request" sent to the targeted window or the window process is brutally "killed"?
2022-12-28 15:39:22 +0100liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-12-28 15:41:06 +0100 <Solid> diep: both; we first ask the window to delete itself, but if it doesn't do that we "brutally kill it"
2022-12-28 15:42:16 +0100 <Solid> (where "if it doesn't do that" means that it doesn't advertise the required deletion atom)
2022-12-28 15:44:50 +0100 <diep> ok thx, because Im developing some native application in Rust using the iced library, and it does not receive the "WindowCloseRequested" event as it should. So I was not sure where is located the problem, but sounds like in the library side.
2022-12-28 15:52:38 +0100 <geekosaur> make sure the window advertises WM_DELETE_WINDOW properly
2022-12-28 15:58:59 +0100 <geekosaur> basically, when the window is open, XPROP it and look at the WM_PROTOCOLS property. if it includes WM_DELETE_WINDOW then we'll send WM_DELETE_WINDOW to the window; if it's not then we call XKill()
2022-12-28 15:59:12 +0100 <geekosaur> er, `xprop`
2022-12-28 16:06:34 +0100 <diep> I see `WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, _NET_WM_PING`
2022-12-28 16:06:44 +0100 <diep> should be good then
2022-12-28 16:07:18 +0100 <geekosaur> then we should be sending WM_DELETE_WINDOW. there's no fallback on the xmonad side where it would XKill() a window if it doesn't respond or anything like that
2022-12-28 16:12:22 +0100 <diep> ok thx for the details, I'll investigate with iced
2022-12-28 16:46:52 +0100 <xmonadtrack> xmonad-contrib Brandon S Allbery KF8NH * v0.17.1-104-g4998e946: fix EWMH titles (2 weeks ago, 1 file, 2+ 3-) https://github.com/xmonad/xmonad-contrib/commit/4998e946ccbb
2022-12-28 16:46:54 +0100 <xmonadtrack> xmonad-contrib Tony Zorman {GitHub} * v0.17.1-106-g55855ccb: Merge pull request #785 from geekosaur/debugwindow-fix-netwm (3 minutes ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad-contrib/commit/55855ccb5fb1
2022-12-28 17:00:09 +0100liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2022-12-28 18:15:52 +0100haasn(~nand@haasn.dev) (Quit: ZNC 1.7.5+deb4 - https://znc.in)
2022-12-28 19:21:16 +0100diep(~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Remote host closed the connection)
2022-12-28 20:08:58 +0100smashgra_(~smashgrab@188.166.8.80) (Quit: ZNC 1.7.2+deb3 - https://znc.in)
2022-12-28 20:09:48 +0100smashgrab(~smashgrab@188.166.8.80)
2022-12-28 20:27:14 +0100mc47(~mc47@xmonad/TheMC47)
2022-12-28 22:32:13 +0100mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-12-28 23:10:58 +0100sogens(~sogens@103.75.11.26)
2022-12-28 23:25:06 +0100sogens(~sogens@103.75.11.26) (Ping timeout: 272 seconds)