Home liberachat/#xmonad: Logs Calendar

Logs on 2022-12-28 (liberachat/#xmonad)

00:04:49 Natch joins (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se)
01:04:59 × ft quits (~ft@i59F541CC.versanet.de) (Ping timeout: 264 seconds)
01:27:10 × tremon quits (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
01:44:24 × sogens quits (~sogens@103.75.11.26) (Ping timeout: 272 seconds)
03:04:59 × banc quits (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 268 seconds)
03:20:43 × td_ quits (~td@83.135.9.15) (Ping timeout: 260 seconds)
03:22:29 td_ joins (~td@83.135.9.57)
03:24:29 banc joins (banc@gateway/vpn/protonvpn/banc)
03:41:27 × terrorjack quits (~terrorjac@2a01:4f8:1c1e:4e8c::) (Quit: The Lounge - https://thelounge.chat)
03:44:04 terrorjack joins (~terrorjac@2a01:4f8:1c1e:4e8c::)
04:09:29 sogens joins (~sogens@103.75.11.26)
09:08:54 × sogens quits (~sogens@103.75.11.26) (Ping timeout: 252 seconds)
13:46:55 tremon joins (~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
14:36:21 diep joins (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c)
14:39:09 <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"?
14:39:22 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
14:41:06 <Solid> diep: both; we first ask the window to delete itself, but if it doesn't do that we "brutally kill it"
14:42:16 <Solid> (where "if it doesn't do that" means that it doesn't advertise the required deletion atom)
14:44:50 <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.
14:52:38 <geekosaur> make sure the window advertises WM_DELETE_WINDOW properly
14:58:59 <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()
14:59:12 <geekosaur> er, `xprop`
15:06:34 <diep> I see `WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, _NET_WM_PING`
15:06:44 <diep> should be good then
15:07:18 <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
15:12:22 <diep> ok thx for the details, I'll investigate with iced
15:46:52 <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
15:46:54 <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
16:00:09 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
17:15:52 × haasn quits (~nand@haasn.dev) (Quit: ZNC 1.7.5+deb4 - https://znc.in)
18:21:16 × diep quits (~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Remote host closed the connection)
19:08:58 × smashgra_ quits (~smashgrab@188.166.8.80) (Quit: ZNC 1.7.2+deb3 - https://znc.in)
19:09:48 smashgrab joins (~smashgrab@188.166.8.80)
19:27:14 mc47 joins (~mc47@xmonad/TheMC47)
21:32:13 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
22:10:58 sogens joins (~sogens@103.75.11.26)
22:25:06 × sogens quits (~sogens@103.75.11.26) (Ping timeout: 272 seconds)
23:02:13 sogens joins (~sogens@103.75.11.26)
23:39:59 × sogens quits (~sogens@103.75.11.26) (Ping timeout: 246 seconds)

All times are in UTC on 2022-12-28.