2026/02/17

2026-02-17 01:15:38 +0100hightower4(~hightower@dh207-83-96.xnet.hr) (Ping timeout: 252 seconds)
2026-02-17 01:19:56 +0100hightower3(~hightower@dh207-83-96.xnet.hr) hightower2
2026-02-17 02:11:48 +0100beastwick(~brian@user/beastwick) beastwick
2026-02-17 02:13:46 +0100 <beastwick> hello, not sure if this is a bug, but I am simply swapping screens with XMonad.Actions.CycleWS swapNextScreen. On one monitor I have tabbed layout, so multiple windows with tabs at the top. When I swap, the workspaces correctly switch, but the tab bar appears over the other workspace and can only be removed if I restart xmonad in place.
2026-02-17 02:14:06 +0100werneta(~werneta@71.83.160.242) werneta
2026-02-17 02:15:53 +0100 <beastwick> oh wait, now it isn't happening not sure why
2026-02-17 02:16:04 +0100 <beastwick> weird
2026-02-17 02:23:11 +0100 <geekosaur> known bug, some layout modifier you're using isn't passing on the Hide message to Tabbed
2026-02-17 02:23:34 +0100 <beastwick> oh :(, can I pass it along, or modify the function?
2026-02-17 02:23:36 +0100 <geekosaur> sadly a lot of layout modifiers don't pass on the Hide or ReleaseResources messages
2026-02-17 02:28:51 +0100 <geekosaur> you'd have to bisect to find the layout modifier that isn't passing them on and make a local copy of it (in ~/.xmonad/lib/XMonad/Layout/whatever.hs) with the handleMessage logic added (see for example https://github.com/xmonad/xmonad-contrib/pull/813/changes#diff-39a8849b1ce55ed5ed86080ca98a422374c…)
2026-02-17 02:29:14 +0100 <beastwick> thanks, this is what I am going to do
2026-02-17 02:29:20 +0100 <beastwick> I already have some other modified classes
2026-02-17 02:29:36 +0100 <geekosaur> if a layout modifier uses the XMonad.Layout.LayoutModifier framework, that already handles them for it
2026-02-17 02:30:33 +0100 <beastwick> oh so, cyclews swapNextScreen can't ensure this, I have to fix the layout modifier itself?
2026-02-17 02:31:00 +0100 <geekosaur> (also if you scroll up on that link, you'll find the old version which actually has the bug in question; note that its handleMess deals only with its own message. I should probably fix that before liskin gets around to reviewing the whole thing)
2026-02-17 02:34:14 +0100 <geekosaur> swapNextScreen itself doesn't process messages, but xmonad sends Hide to the workspace being swapped and then when it's redrawn on its new screen the tabs are recreated
2026-02-17 02:34:26 +0100 <geekosaur> something in the layout stack isn't passing on Hide to Tabbed
2026-02-17 02:34:40 +0100 <geekosaur> so the tabs stay where they were drawn on the old screen
2026-02-17 02:35:16 +0100 <geekosaur> Tabbed itself handles these correctly (well, Decoration handles them for it) but it has to receive them
2026-02-17 02:36:26 +0100 <geekosaur> so you need to take a look at your layoutHook and in particular any modifiers before the actual layouts; usually these are modifier1 $ modifier 2 $ … $ (layout ||| layout ||| …)
2026-02-17 02:42:11 +0100 <geekosaur> sorry, it actually sends ReleaseResources so the windows are removed and later recreated
2026-02-17 02:42:30 +0100 <geekosaur> but generally people don't handle either in layout modifiers 😦
2026-02-17 02:56:02 +0100 <beastwick> much thanks, so is it an issue in the library itself, or perhaps something I can pass via my layout modifier hook?
2026-02-17 02:56:24 +0100 <beastwick> or well, you are saying that tabbed layout might not handle messages?
2026-02-17 03:13:34 +0100 <geekosaur> you can't pass it via your layoutHook, and Tabbed is already doing the right thing. something *leading to* Tabbed isn't doing the right thing, and you can't just wire around it without losing that layout modifier completely
2026-02-17 03:14:28 +0100 <geekosaur> you meed to find out which layout modifier is swallowing the message and make a local copy modified to pass the message on, and file an issue about it so we can fix it here (or open a PR with your modified copy)
2026-02-17 03:15:55 +0100 <geekosaur> https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Layout/PerScreen.hs#L70-L72 this is a layout modifier that swallows messages instead of passing them on (for which I already have a fix in a PR)
2026-02-17 03:21:20 +0100werneta(~werneta@71.83.160.242) (Quit: Lost terminal)
2026-02-17 03:28:26 +0100 <geekosaur> one of the things I would really like to do but don't see a good way to do with the way we currently do layout messages is message tracing
2026-02-17 03:35:09 +0100freedrul1(~deploy@167.99.155.33) (Server closed connection)
2026-02-17 03:50:25 +0100freedrull(~deploy@167.99.155.33) freedrull
2026-02-17 04:10:46 +0100td_(~td@i5387093C.versanet.de) (Ping timeout: 244 seconds)
2026-02-17 04:12:46 +0100td_(~td@i53870928.versanet.de) td_
2026-02-17 04:41:48 +0100werneta(~werneta@71.83.160.242) werneta
2026-02-17 04:47:09 +0100FatBoyXPC(~FatBoyXPC@user/fatboyxpc) (Server closed connection)
2026-02-17 04:48:21 +0100FatBoyXPC(~FatBoyXPC@user/fatboyxpc) FatBoyXPC
2026-02-17 05:59:54 +0100werneta_(~werneta@71.83.160.242) werneta
2026-02-17 06:03:15 +0100Forkk13(~forkk@li926-228.members.linode.com) (Ping timeout: 245 seconds)
2026-02-17 06:15:10 +0100werneta(~werneta@71.83.160.242) (Quit: Lost terminal)
2026-02-17 06:19:55 +0100sajenim(~sajenim@user/sajenim) (Ping timeout: 245 seconds)
2026-02-17 06:20:58 +0100lambdabot(~lambdabot@haskell/bot/lambdabot) (Read error: Connection reset by peer)
2026-02-17 06:20:58 +0100sajenim(~sajenim@user/sajenim) sajenim
2026-02-17 06:25:36 +0100lambdabot(~lambdabot@haskell/bot/lambdabot) lambdabot
2026-02-17 07:36:36 +0100werneta_(~werneta@71.83.160.242) (Quit: Lost terminal)
2026-02-17 08:09:28 +0100ml|(~ml|@user/ml/x-5298235) (Ping timeout: 244 seconds)
2026-02-17 08:23:50 +0100ml|(~ml|@user/ml/x-5298235) ml|
2026-02-17 10:13:02 +0100ft(~ft@p4fc2afab.dip0.t-ipconnect.de) (Quit: leaving)
2026-02-17 13:32:09 +0100smashgrab(~smashgrab@188.166.8.80) (Server closed connection)
2026-02-17 13:32:52 +0100smashgrab(~smashgrab@188.166.8.80) smashgrab
2026-02-17 14:03:43 +0100T_X(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2026-02-17 14:04:20 +0100T_X(~T_X@diktynna.open-mesh.org) T_X
2026-02-17 14:51:01 +0100Enrico63(~Enrico63@host-79-56-90-180.retail.telecomitalia.it) Enrico63
2026-02-17 14:51:40 +0100hightower4(~hightower@dh207-83-96.xnet.hr) hightower2
2026-02-17 14:54:13 +0100hightower3(~hightower@dh207-83-96.xnet.hr) (Ping timeout: 255 seconds)
2026-02-17 15:01:41 +0100hightower3(~hightower@cpe-94-253-236-205.st.cable.xnet.hr) hightower2
2026-02-17 15:03:32 +0100hightower4(~hightower@dh207-83-96.xnet.hr) (Ping timeout: 265 seconds)
2026-02-17 15:05:48 +0100hightower3(~hightower@cpe-94-253-236-205.st.cable.xnet.hr) (Read error: Connection reset by peer)
2026-02-17 15:05:58 +0100hightower3(~hightower@cpe-94-253-236-205.st.cable.xnet.hr) hightower2
2026-02-17 15:07:22 +0100T_X_(~T_X@diktynna.open-mesh.org) T_X
2026-02-17 15:07:28 +0100T_X(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2026-02-17 15:32:22 +0100rekahsoft(~rekahsoft@76.67.111.168) rekahsoft
2026-02-17 15:38:12 +0100hightower3(~hightower@cpe-94-253-236-205.st.cable.xnet.hr) (Ping timeout: 264 seconds)
2026-02-17 17:40:41 +0100Enrico63(~Enrico63@host-79-56-90-180.retail.telecomitalia.it) (Ping timeout: 272 seconds)
2026-02-17 17:57:05 +0100Enrico63(~Enrico63@host-79-56-90-180.retail.telecomitalia.it) Enrico63
2026-02-17 17:58:00 +0100Enrico63(~Enrico63@host-79-56-90-180.retail.telecomitalia.it) (Client Quit)
2026-02-17 19:04:10 +0100ChubaDuba(~ChubaDuba@5.167.118.198) ChubaDuba
2026-02-17 19:47:33 +0100ChubaDuba(~ChubaDuba@5.167.118.198) (Quit: WeeChat 4.8.1)
2026-02-17 19:47:50 +0100ChubaDuba(~ChubaDuba@5.167.118.198) ChubaDuba
2026-02-17 19:54:11 +0100ChubaDuba(~ChubaDuba@5.167.118.198) (Quit: WeeChat 4.8.1)
2026-02-17 19:54:24 +0100ChubaDuba(~ChubaDuba@5.167.118.198) ChubaDuba
2026-02-17 19:58:44 +0100ChubaDuba(~ChubaDuba@5.167.118.198) (Ping timeout: 252 seconds)
2026-02-17 20:06:59 +0100de-vri-es(~de-vri-es@voyager.de-vri.es) (Server closed connection)
2026-02-17 20:07:21 +0100de-vri-es(~de-vri-es@voyager.de-vri.es) de-vri-es
2026-02-17 20:52:08 +0100ChubaDuba(~ChubaDuba@5.167.118.198) ChubaDuba
2026-02-17 20:56:29 +0100ChubaDuba(~ChubaDuba@5.167.118.198) (Ping timeout: 252 seconds)