| 2024-06-26 01:00:20 +0200 | ft | (~ft@p4fc2ab80.dip0.t-ipconnect.de) |
| 2024-06-26 01:12:13 +0200 | mekeor | (~user@2001:a61:25ed:a301:ad37:1d69:745f:dbe2) (Quit: towards emacs as interface to cybernetic council communism) |
| 2024-06-26 03:15:35 +0200 | kaskal | (~kaskal@213-147-165-88.nat.highway.webapn.at) (Ping timeout: 252 seconds) |
| 2024-06-26 04:49:05 +0200 | td_ | (~td@i53870933.versanet.de) (Ping timeout: 252 seconds) |
| 2024-06-26 04:51:08 +0200 | td_ | (~td@i53870920.versanet.de) |
| 2024-06-26 07:03:09 +0200 | <haskellbridge> | <iqubic (she/her)> Turns out you can just let polybar read the ewmh atoms that XMonad reports and things just work. |
| 2024-06-26 07:48:15 +0200 | ft | (~ft@p4fc2ab80.dip0.t-ipconnect.de) (Quit: leaving) |
| 2024-06-26 09:26:20 +0200 | <haskellbridge> | <iqubic (she/her)> I also have no idea what ewmh trickery is going on, but somehow Polybar can tell XMonad to jump to a specific workspace, or also go to the next/previous workspace. That's cool, I guess. |
| 2024-06-26 10:01:28 +0200 | <geekosaur> | it's sending _NET_CURRENT_DESKTOP ClientMessages to the root window; EwmhDesktops listens for those and switches workspaces |