2024/06/25

2024-06-25 01:21:01 +0200mekeor`(~user@2001:a61:25ed:a301:ad37:1d69:745f:dbe2)
2024-06-25 01:22:27 +0200mekeor(~user@2001:a61:24d2:9401:96ac:ce90:6d78:efe3) (Ping timeout: 264 seconds)
2024-06-25 01:25:40 +0200mekeor`mekeor
2024-06-25 02:06:59 +0200mekeor(~user@2001:a61:25ed:a301:ad37:1d69:745f:dbe2) (Quit: bad [...] major browsers)
2024-06-25 02:39:37 +0200 <haskellbridge> <iqubic (she/her)> How exactly does ewmh work? How does xmonad set which workspaces have windows on them?
2024-06-25 02:39:52 +0200 <haskellbridge> <iqubic (she/her)> Is there just some property of the root window I can query?
2024-06-25 02:44:40 +0200 <geekosaur> it's kinda backwards. there's no mater list; every client has a _NET_WM_DESKTOP with the EWMH workspace number (index into _NET_DESKTOP_NAMES) as its value
2024-06-25 02:46:01 +0200 <geekosaur> when you use xmonad's PP instead of EWMH, xmonad can query the Stack of each workspace; programs that use EWMH have to use XQueryTree and then query every top level window returned
2024-06-25 02:46:19 +0200 <haskellbridge> <iqubic (she/her)> I see.
2024-06-25 02:46:58 +0200 <haskellbridge> <iqubic (she/her)> From what I'm seeing in the polybar source, it seems to use the XQueryTree.
2024-06-25 02:56:22 +0200 <geekosaur> actually it looks like it can get a window list from _NET_CLIENT_LIST on the root window, but it still has to query them for _NET_WM_DESKTOP to see where they are
2024-06-25 02:57:21 +0200 <geekosaur> but many programs might not bother having both paths since it has to fall back to XQueryTree if _NET_CLIENT_LIST isn't in _NET_SUPPORTED or not present on the root window
2024-06-25 04:44:30 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2024-06-25 04:48:35 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2024-06-25 04:50:26 +0200td_(~td@i5387092F.versanet.de) (Ping timeout: 256 seconds)
2024-06-25 04:50:35 +0200Leary(~Leary@user/Leary/x-0910699)
2024-06-25 04:52:21 +0200td_(~td@i53870933.versanet.de)