2026/04/30

Newest at the top

2026-04-30 13:51:01 +0000vados(~vados@46-133-18-172.mobile.vf-ua.net)
2026-04-30 11:18:13 +0000tremon(~tremon@83.80.159.219) tremon
2026-04-30 10:46:36 +0000haskellbridge(~hackager@96.28.224.214) hackager
2026-04-30 10:41:02 +0000haskellbridge(~hackager@96.28.224.214) (Read error: Connection reset by peer)
2026-04-30 08:46:22 +0000berberman(~berberman@user/berberman) berberman
2026-04-30 08:45:48 +0000berberman(~berberman@user/berberman) (Client Quit)
2026-04-30 08:44:31 +0000berberman(~berberman@user/berberman) berberman
2026-04-30 08:43:47 +0000berberman(~berberman@user/berberman) (Quit: ZNC 1.10.1 - https://znc.in)
2026-04-30 08:37:50 +0000 <liskin> L29Ah: which is still as dead as it's always been, and also fundamentally the wrong design
2026-04-30 07:42:26 +0000vados(~vados@46-133-18-172.mobile.vf-ua.net) (Ping timeout: 244 seconds)
2026-04-30 07:33:54 +0000ft(~ft@p200300cf3f4f28002264268f01ab0284.dip0.t-ipconnect.de) (Quit: leaving)
2026-04-30 07:01:34 +0000Enrico63(~Enrico63@85.255.235.90) Enrico63
2026-04-30 04:39:08 +0000RMSBach(~RMSBach@2603:6013:9b40:6f2::1040) RMSBach
2026-04-30 04:15:35 +0000RMSBach(~RMSBach@2603:6013:9b40:6f2::1040) (Ping timeout: 245 seconds)
2026-04-30 02:11:00 +0000gwentpl(~gwpl@user/gwentpl) (Ping timeout: 245 seconds)
2026-04-30 02:10:51 +0000spwl(~gwpl@user/gwentpl) gwentpl
2026-04-29 23:58:14 +0000 <liskin> Train connections from London are awful but one can always fly. Assuming there's still jet fuel - I haven't been watching the news lately.
2026-04-29 23:57:42 +0000 <liskin> Anyway, ZuriHac is a thing. I'm still good to go. Athough it's in like 5 weeks so that's a bit scary. :-D
2026-04-29 23:53:59 +0000 <L29Ah> this reminds me of https://github.com/waymonad/waymonad
2026-04-29 23:52:25 +0000 <liskin> I've been reluctant to merge Leary's core patches that change when stuff is evaluated because I was worried contrib will break. This is not and should not be a concern now - the core's been mostly the same for almost 2 decades. Surely we can learn from that and take a while to iterate on what it might look like going forward.
2026-04-29 23:50:45 +0000 <liskin> If anything, this is an opportunity to revisit some core design decisions.
2026-04-29 23:48:57 +0000 <liskin> Fuck expectations, fuck xmonad-contrib. Start with the basics, iterate, tweet/toot/blog/whatever about progress.
2026-04-29 23:48:14 +0000 <liskin> I think I'm in agreement with Ivan (c​olonelpanic) on this. We don't need to overthink this - just roll the sleeves up and get hacking, just like people did back 20 years ago.
2026-04-29 22:38:06 +0000tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2026-04-29 21:21:17 +0000vados(~vados@46-133-18-172.mobile.vf-ua.net)
2026-04-29 21:06:30 +0000vados(~vados@46-133-1-158.mobile.vf-ua.net) (Read error: Connection reset by peer)
2026-04-29 20:12:04 +0000haskellbridge(~hackager@96.28.224.214) hackager
2026-04-29 20:11:45 +0000haskellbridge(~hackager@96.28.224.214) (Ping timeout: 244 seconds)
2026-04-29 19:13:20 +0000ft(~ft@p200300cf3f4f28002264268f01ab0284.dip0.t-ipconnect.de) ft
2026-04-29 18:57:02 +0000 <geekosaur> (we're "abusing" an ancient configuration system for window matching that nobody uses any more even on x11 and doesn't exist at all on wayland)
2026-04-29 18:56:12 +0000 <geekosaur> it seems pretty likely that wayland will need to be a separate effort, because even as a river plugin it would run into things like manageHooks not really working the same way in a Wayland world
2026-04-29 18:12:43 +0000 <haskellbridge> <c​olonelpanic> I have some time to throw at this, but I guess I'd like some input from people about what sort of thing would be more likely to draw support from the existing xmonad community
2026-04-29 18:11:44 +0000 <haskellbridge> <c​olonelpanic> this might be crazy, but would it be crazy to try to write a core that aims to actually support x11 and River somehow, maybe by using xcb instead of XLib?
2026-04-29 18:10:50 +0000 <haskellbridge> <c​olonelpanic> are there design tweaks to the xmonad paradigm that any effort here that should be made, or should we just aim for similarity to make adaptation of existing xmonad-contrib as easy as possible
2026-04-29 18:10:02 +0000 <haskellbridge> <c​olonelpanic> yeah i guess the question is like how compatible with xmonad should any migration try to be
2026-04-29 18:08:29 +0000 <geekosaur> right, but some of the ones that aren't are the more popular ones (e.g. `Tabbed`)
2026-04-29 18:07:37 +0000 <haskellbridge> <c​olonelpanic> theyre are a lot layouts that are more pure though and would be a bit easier to work with
2026-04-29 17:47:51 +0000 <geekosaur> (sadly Spencer didn't realize xcb was a thing when he wrote xmonad; if he had, that would be much easier to migrate)
2026-04-29 17:47:18 +0000 <geekosaur> yeh, the problem there isn't the core. the problem is that many things (in particular layouts) do window server operations, and XLib and libwayland are very different beasts
2026-04-29 17:44:28 +0000 <haskellbridge> <c​olonelpanic> I haven't looked in to it in detail but I think it might be possible to minimize that amount of api change to the core
2026-04-29 17:44:04 +0000 <haskellbridge> <c​olonelpanic> and I think migration for a lot of stuff probably wont be too hard
2026-04-29 17:43:38 +0000 <haskellbridge> <c​olonelpanic> yes of course, but i think it could still feel pretty good, with just the "core of contrib"
2026-04-29 17:43:10 +0000 <geekosaur> I mean, the core is _really_ plain
2026-04-29 17:43:02 +0000 <geekosaur> it could be, but without contrib xmonad loses a lot of what it offers
2026-04-29 17:42:31 +0000 <haskellbridge> <c​olonelpanic> geekosaur: of course, but its also something that could be done incrementally
2026-04-29 17:21:22 +0000gwentpl(~gwpl@user/gwentpl) gwentpl
2026-04-29 17:19:19 +0000gwentpl(~gwpl@user/gwentpl) (Read error: Connection reset by peer)
2026-04-29 16:52:39 +0000gwentpl(~gwpl@user/gwentpl) gwentpl
2026-04-29 16:38:39 +0000gwentpl(~gwpl@user/gwentpl) (Read error: Connection reset by peer)
2026-04-29 15:22:58 +0000vados(~vados@46-133-1-158.mobile.vf-ua.net)