IRCBrowse

2023/04/19

2023-04-19 00:07:12 +0200pharonix71(~pharonix7@user/pharonix71) (Remote host closed the connection)
2023-04-19 00:07:53 +0200 <jabuxas> i have interesting issues, one i already made an issue on github and im just asking for clearing as to why it might happen
2023-04-19 00:07:55 +0200 <jabuxas> one of the issues was that game launchers made xmonad overloaded, sluggish and it didnt respond, which, after disabling windowedFullscreenFixEventHook and fullscreenSupport, that went away
2023-04-19 00:07:57 +0200 <jabuxas> one other is league of legends client, which after being touched (receiving any input) tiled itself (even though I specifically made it float), and the answer to that was removing ewmhFullscreen.
2023-04-19 00:08:07 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-19 00:08:19 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2023-04-19 00:08:34 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-19 00:09:10 +0200 <jabuxas> i tried looking at source code but couldn't find the exact reason for why that happened with my skills
2023-04-19 00:09:21 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2023-04-19 00:32:05 +0200jabuxas(~jabuxas@user/jabuxas) (Ping timeout: 260 seconds)
2023-04-19 00:34:23 +0200 <geekosaur> I have no idea what to do about an xlib crash…
2023-04-19 00:34:36 +0200 <geekosaur> switching to xcb isn't really an option at this point
2023-04-19 00:35:30 +0200catman(~catman@user/catman)
2023-04-19 00:39:02 +0200 <L29Ah> fix xlib
2023-04-19 00:39:14 +0200 <L29Ah> are you sure it's xlib tho?
2023-04-19 00:41:37 +0200 <geekosaur> it's the only place that can produce that error
2023-04-19 00:42:14 +0200 <geekosaur> we don't make poly calls, which is the only other thing that can produce that error
2023-04-19 00:46:22 +0200 <geekosaur> and RH isn't about to fix xlib, that would be admitting that there are still people that don't run Wayland
2023-04-19 00:48:59 +0200 <L29Ah> alternatively someone could fix https://github.com/qutebrowser/qutebrowser/issues/5108 and then we can pretend like xmonad has no bugs
2023-04-19 00:49:14 +0200 <L29Ah> geekosaur: https://gitlab.freedesktop.org/xorg/lib/libx11/-/commits/master too many fresh commits for that hypothesis
2023-04-19 00:49:46 +0200 <L29Ah> also, why is it only triggered by Tabbed?
2023-04-19 00:50:02 +0200 <L29Ah> i'd expect things like my huge window matching rules look up WM_NAME as well
2023-04-19 00:52:53 +0200 <geekosaur> do they use `title`?
2023-04-19 00:53:04 +0200 <geekosaur> (it's usually a bad idea, especially for browsers)
2023-04-19 00:54:01 +0200 <L29Ah> geekosaur: https://github.com/l29ah/xmonad-config/blob/master/xmonad.hs#L260
2023-04-19 00:55:05 +0200 <geekosaur> it's in a composeOne and thereby skipped because https://github.com/l29ah/xmonad-config/blob/master/xmonad.hs#L253 matched
2023-04-19 00:59:06 +0200 <L29Ah> i wonder why xmonad doesn't crash when qutebrowser is already running
2023-04-19 01:00:03 +0200 <L29Ah> i can restart xmonad after crashing and it's fine with its Tabbed qutebrowser
2023-04-19 01:11:23 +0200mncheck(~mncheck@193.224.205.254) (Ping timeout: 246 seconds)
2023-04-19 01:11:54 +0200 <geekosaur> https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Util/NamedWindows.hs#L52-L53 from updateDeco
2023-04-19 01:12:18 +0200 <geekosaur> which is called when the tab is created and probably not again until you do something that resizes the tab
2023-04-19 01:12:51 +0200 <L29Ah> but a tab is created each time xmonad is restarted
2023-04-19 01:13:05 +0200 <L29Ah> s/rest/st/
2023-04-19 01:13:06 +0200 <geekosaur> created, or left around?
2023-04-19 01:13:46 +0200 <L29Ah> geekosaur: what do you mean "left around"? xmonad needs to create all them decorations when it starts up
2023-04-19 01:21:23 +0200 <geekosaur> I thought it had no chance to clean up the existing tabs when it died (the abort is inside xcb as invoked by xlib) but apparently it's not marking them persistent
2023-04-19 01:21:46 +0200 <geekosaur> (I'm testing stuff in my sandbox as I go;p the tabs definitely disappear before xmonad restarts)
2023-04-19 01:23:08 +0200 <L29Ah> ok, xprop says the WM_NAME is much smaller
2023-04-19 01:23:21 +0200 <L29Ah> maybe qutebrowser dumps the huge one and then trims it afterwards, idk
2023-04-19 01:24:23 +0200 <geekosaur> the trashed tab you showed in the beginning strongly suggests xmonad was trying to render the whole 350+k string in the tab
2023-04-19 01:25:01 +0200 <L29Ah> if it tried to render it, then it fetched it
2023-04-19 01:25:24 +0200 <geekosaur> yeh
2023-04-19 01:25:51 +0200 <geekosaur> also I note that qutebrowser is trying to render the string at first and then the render thread crashes
2023-04-19 01:26:12 +0200 <geekosaur> which is why it's not happening on restart; the tab has an error string instead
2023-04-19 01:29:15 +0200 <L29Ah> > the render thread crashes
2023-04-19 01:29:16 +0200 <L29Ah> does it? i think the URL itself is about the render thread crashing
2023-04-19 01:29:17 +0200 <lambdabot> error:
2023-04-19 01:29:17 +0200 <lambdabot> Variable not in scope: the :: (Doc -> String) -> t0 -> t1 -> terror:
2023-04-19 01:29:17 +0200 <lambdabot> • Variable not in scope: thread
2023-04-19 01:29:32 +0200 <L29Ah> so you might be confusing it
2023-04-19 01:30:10 +0200 <geekosaur> only if it's a quine; look at the url it claims to be opening
2023-04-19 01:30:14 +0200 <L29Ah> and xprop is showing a trimmed version of the URL that is yanked with yy
2023-04-19 01:30:32 +0200 <L29Ah> the one that gets yanked is huge
2023-04-19 01:32:36 +0200 <geekosaur> yes, and includes: Error while opening https://blueprint.bryanjohnson.co.uk…
2023-04-19 01:32:43 +0200 <L29Ah> found where the qutebrowser title is set, but no idea why is it trimmed
2023-04-19 01:32:45 +0200 <L29Ah> // self.widget.window().setWindowTitle(title)
2023-04-19 01:35:30 +0200 <geekosaur> damn, maybe this thing is a quine
2023-04-19 01:36:00 +0200 <geekosaur> but still, that means it starts out showing the url and then changes it to the page title
2023-04-19 01:36:26 +0200 <geekosaur> so it's still shoveled 389k into WM_NAME and/or _NET_WM_NAME
2023-04-19 01:41:03 +0200 <geekosaur> and right, if I hit the Try again link it reports it couldn't open the url I saw embedded in it
2023-04-19 01:41:30 +0200 <geekosaur> and does not crash
2023-04-19 01:43:42 +0200 <geekosaur> hm, it's a bit late for liskin to be around but… around?
2023-04-19 01:49:47 +0200 <liskin> About to fall asleep
2023-04-19 01:51:48 +0200 <geekosaur> oh. check back here tomorrow then
2023-04-19 01:52:05 +0200 <L29Ah> i brainfarted at https://github.com/qutebrowser/qutebrowser/issues/5108 now gotta go sleep as well
2023-04-19 01:52:07 +0200 <geekosaur> I'm trying to gdb to verify where we're crashing but I think it's Xlib
2023-04-19 02:00:16 +0200 <geekosaur> argh. gdb is stuck at "reading symbols"
2023-04-19 02:09:46 +0200 <geekosaur> I'll let it run overnight, hopefully I can get something halfway useful out of it tomorrow
2023-04-19 02:57:18 +0200 <geekosaur> it's not even using cpu 😞
2023-04-19 03:00:09 +0200 <geekosaur> wtf, SIGTTOU. it's attached to a terminal…
2023-04-19 03:18:00 +0200 <geekosaur> I attached to it from outside instead. and it doesn't crash
2023-04-19 03:18:13 +0200 <geekosaur> I hate these kinds of bugs…
2023-04-19 03:19:27 +0200 <geekosaur> and the tab is completely empty
2023-04-19 03:20:04 +0200 <geekosaur> it's 2130, I'm going to bed and will try to sort this tomorrow
2023-04-19 03:43:42 +0200hightower3(~hightower@213.202.92.246)
2023-04-19 03:46:05 +0200hightower2(~hightower@230-130.dsl.iskon.hr) (Ping timeout: 240 seconds)
2023-04-19 04:07:24 +0200td_(~td@i53870902.versanet.de) (Ping timeout: 255 seconds)
2023-04-19 04:09:15 +0200td_(~td@i5387091D.versanet.de)
2023-04-19 06:09:25 +0200catman(~catman@user/catman) (Ping timeout: 240 seconds)
2023-04-19 06:50:25 +0200piele(~piele@tbonesteak.creativeserver.net) (Remote host closed the connection)
2023-04-19 06:51:37 +0200piele(~piele@tbonesteak.creativeserver.net)
2023-04-19 08:28:23 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy) (Ping timeout: 255 seconds)
2023-04-19 08:30:21 +0200stellacy(~stellacy@gateway/tor-sasl/stellacy)
2023-04-19 08:43:34 +0200mncheck(~mncheck@193.224.205.254)
2023-04-19 09:16:18 +0200 <geekosaur> (bleh, why am I up at 0300) just crashed it trying to put it into synchronous mode, oops. why I shouldn't try to debug at 0300
2023-04-19 09:17:04 +0200 <geekosaur> (xmonad needs a --sync option for debugging…)
2023-04-19 09:18:36 +0200 <geekosaur> (would also have helped with debugging the windowNavigation issue)
2023-04-19 09:19:46 +0200 <geekosaur> aaaaaand it crashed when I restarted qutebrowser in a new session. oy
2023-04-19 09:20:47 +0200 <geekosaur> yeh, it's crashing every time now. L29Ah I think you just got lucky
2023-04-19 09:20:58 +0200 <geekosaur> and/or there's a timing constraint
2023-04-19 09:27:32 +0200 <geekosaur> we don't bind XSynchronize 😞
2023-04-19 09:27:40 +0200 <geekosaur> deal tomorrow
2023-04-19 10:06:38 +0200cfricke(~cfricke@user/cfricke)
2023-04-19 10:07:36 +0200 <geekosaur> or realize I can't get back to sleep…
2023-04-19 10:07:38 +0200 <geekosaur> welp
2023-04-19 10:07:41 +0200 <geekosaur> #10 0x00007fa9d08115fb in XftDrawStringUtf8 () from /lib/x86_64-linux-gnu/libXft.so.2
2023-04-19 10:10:34 +0200 <geekosaur> so it is indeed not in retrieving WM_NAME, it's in trying to render it in the tab
2023-04-19 10:13:42 +0200bla(~bla@79.191.151.29.ipv4.supernova.orange.pl) (Ping timeout: 255 seconds)
2023-04-19 10:23:16 +0200mc47(~mc47@xmonad/TheMC47)
2023-04-19 10:30:25 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de) (Ping timeout: 250 seconds)
2023-04-19 10:35:22 +0200 <geekosaur> gonna hate trying to figure out why the Shrinker isn't; I always get crosseyed looking at those damned things
2023-04-19 11:00:12 +0200guazai[m](~guazaimat@2001:470:69fc:105::3:3254) (Quit: You have been kicked for being idle)
2023-04-19 11:00:14 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle)
2023-04-19 11:00:14 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-19 11:00:14 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-04-19 11:17:25 +0200hightower3(~hightower@213.202.92.246) (Ping timeout: 240 seconds)
2023-04-19 11:21:42 +0200 <geekosaur> okay, think I've sorted it (and it's a slow piece of junk, it shrinks a character at a time from a list which means it's quadratic. on a 389K String…)
2023-04-19 11:21:56 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-19 11:22:04 +0200 <geekosaur> (and doesn't handle multiline strings at all afaict)
2023-04-19 11:22:08 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2023-04-19 11:22:22 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-19 11:26:00 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-04-19 11:33:01 +0200cfricke(~cfricke@user/cfricke)
2023-04-19 12:27:27 +0200 <L29Ah> sanitizing title before feeding it to a shrinker sounds good to me
2023-04-19 12:27:48 +0200 <L29Ah> well, it would be nicer to migrate from String, but it's good enough
2023-04-19 13:47:45 +0200td_(~td@i5387091D.versanet.de) (Ping timeout: 240 seconds)
2023-04-19 13:47:59 +0200td_(~td@i5387091D.versanet.de)
2023-04-19 15:12:34 +0200hightower2(~hightower@95.168.105.23)
2023-04-19 15:37:48 +0200hightower2(~hightower@95.168.105.23) (Read error: Connection reset by peer)
2023-04-19 16:00:56 +0200catman(~catman@user/catman)
2023-04-19 17:23:01 +0200catman(~catman@user/catman) (Ping timeout: 240 seconds)
2023-04-19 17:28:21 +0200 <xmonadtrack> New xmonad-contrib branch created: pull/810 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/810
2023-04-19 17:30:27 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-04-19 17:30:33 +0200 <L29Ah> :*
2023-04-19 17:36:26 +0200 <L29Ah> hmm xmonad hangs for a few secs even with this patch
2023-04-19 17:36:30 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-04-19 17:36:50 +0200 <L29Ah> but that's good enough i guess
2023-04-19 17:44:27 +0200 <geekosaur> seemed pretty quick here
2023-04-19 17:45:21 +0200 <L29Ah> i7-8550U laptop here
2023-04-19 17:45:35 +0200 <geekosaur> mine is an older i5
2023-04-19 17:45:48 +0200catman(~catman@user/catman)
2023-04-19 17:45:50 +0200 <geekosaur> and I'm running it in a xephyr in a test harness
2023-04-19 17:47:57 +0200 <L29Ah> i guess that might be due to the fact i have several such tabs in my qutebrowser
2023-04-19 17:48:09 +0200 <L29Ah> and it blinks them
2023-04-19 17:55:24 +0200catman(~catman@user/catman) (Ping timeout: 255 seconds)
2023-04-19 18:00:08 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-19 18:00:08 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle)
2023-04-19 18:00:08 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-04-19 18:06:42 +0200 <geekosaur> what I'm actually seeing is qutebrowser hangs for a second or two. that's not under xmonad's control; drawing is solely between the client and the X server, xmonad can't even know it's happening without e.g. taking a couple of screenshots and comparing them
2023-04-19 18:06:54 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-19 18:07:07 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2023-04-19 18:07:22 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-19 18:11:07 +0200 <geekosaur> and in unrelated news it seems the SSA is just being confusing. there is one more hoop to jump through but it's actually irrelevant. in practice I won
2023-04-19 18:11:22 +0200 <geekosaur> so another few months and then I have income
2023-04-19 18:11:36 +0200 <geekosaur> and can start paying back what I've taken 🙂
2023-04-19 18:54:38 +0200 <xmonadtrack> xmonad-contrib Brandon S Allbery KF8NH * v0.17.1-151-g87ae269b: Put a cap on window names (2 hours ago, 1 file, 6+ 2-) https://github.com/xmonad/xmonad-contrib/commit/87ae269b8279
2023-04-19 19:19:04 +0200jeeeun(~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat)
2023-04-19 19:20:25 +0200jeeeun(~jeeeun@78.40.148.178)
2023-04-19 19:37:01 +0200L29Ah(~L29Ah@wikipedia/L29Ah) ()
2023-04-19 19:59:02 +0200jabuxas(~jabuxas@user/jabuxas)
2023-04-19 19:59:23 +0200 <jabuxas> hello
2023-04-19 20:02:56 +0200 <geekosaur> hi
2023-04-19 20:03:38 +0200 <geekosaur> I saw your messages yesterday but you left before I could reply
2023-04-19 20:04:35 +0200 <geekosaur> unfortunately while I think there was an overhaul of ewmhFullscreen recently I can't find it
2023-04-19 20:04:48 +0200 <geekosaur> are you running a released version or from git?
2023-04-19 20:05:37 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2023-04-19 20:17:44 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de)
2023-04-19 21:34:53 +0200 <jabuxas> git
2023-04-19 21:36:12 +0200 <jabuxas> yea i had a blackout yesterday that's why
2023-04-19 21:37:05 +0200 <jabuxas> xmonad contrib commit 673de11ca876a4a58cae3a4d52e36260f66aa6cc
2023-04-19 21:39:03 +0200 <jabuxas> the problem with ewmh fullscreen specifically was that it was tiling the game client when it shouldnt
2023-04-19 21:39:16 +0200 <geekosaur> %gitcontrib 673de11ca87
2023-04-19 21:39:16 +0200 <xmonadtrack> xmonad-contrib Tomas Janousek {GitHub} * v0.17.1-150-g673de11c: Merge pull request #768 from liskin/fullscreen-hooks (3 weeks ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad-contrib/commit/673de11ca876
2023-04-19 21:40:34 +0200 <geekosaur> does it behave if you revert that locally?
2023-04-19 21:43:02 +0200 <geekosaur> you probably want liskin but I don't know if he's around
2023-04-19 21:52:07 +0200 <jabuxas> how would i go about reverting locally? switching commits in stack.yaml and `stack build`?
2023-04-19 21:53:31 +0200 <jabuxas> i dont think that would change anything since i've had this problem for at least 3/4 months, but can do it anyway
2023-04-19 21:57:33 +0200 <geekosaur> oh. so that was just the commit you're on now?
2023-04-19 21:57:42 +0200 <jabuxas> yes
2023-04-19 21:58:47 +0200 <geekosaur> I'd be interested in knowing if the client still is asserting _NET_WM_STATE_FULLSCREEN on the window
2023-04-19 21:59:46 +0200 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L246 or similar
2023-04-19 22:00:51 +0200 <geekosaur> (I have a bunch of debugging / "how do I build a manageHook for this?" keybinds)
2023-04-19 22:02:31 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Ping timeout: 260 seconds)
2023-04-19 22:03:52 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2023-04-19 22:08:32 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2023-04-19 22:15:26 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2023-04-19 22:21:19 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca)
2023-04-19 22:33:05 +0200 <jabuxas> let me add that and test
2023-04-19 22:33:07 +0200 <jabuxas> do you want me to test with or without ewmhFullscreen?
2023-04-19 22:37:02 +0200 <jabuxas> https://dpaste.org/yAykK
2023-04-19 22:40:07 +0200 <geekosaur> what I'm interested in is whether the window that gets incorrectly tiled still has _NET_WM_STATE_FULLSCREEN in _NET_WM_STATE
2023-04-19 22:40:18 +0200 <geekosaur> so yes, with
2023-04-19 22:40:52 +0200 <jabuxas> this is with https://dpaste.org/zOs4g
2023-04-19 22:41:20 +0200 <geekosaur> actually according to that paste neither window has _NET_WM_STATE at all
2023-04-19 22:41:45 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 240 seconds)
2023-04-19 22:44:03 +0200 <geekosaur> I wonder if it's just sending the message without setting the state, which is an EWMH violation
2023-04-19 22:44:18 +0200 <jabuxas> well its possible to see that tiles automatically on the screen dimensions of the log, even though managehook tells it not to
2023-04-19 22:44:54 +0200 <jabuxas> https://dpaste.com/CF9ALU8GE#line-368
2023-04-19 22:48:11 +0200 <geekosaur> hm. some things have to be done in a particular order or they get undone. what happens if you swap the doShift and the doCenterFloat?
2023-04-19 22:52:45 +0200 <jabuxas> still happens on interact
2023-04-19 22:54:19 +0200 <geekosaur> hm. I'm back to thinking this is related to _NET_WM_STATE
2023-04-19 22:55:13 +0200 <geekosaur> "on interact" is weird
2023-04-19 22:55:40 +0200 <jabuxas> so if I'm understanding correctly, ewmhFullscreen would fullscreen an application if asked, so that's why disabling it fixes the issue, because maybe if the game client asks to fullscreen, xmonad just doesn't do it?
2023-04-19 22:55:54 +0200 <geekosaur> that said I have something similarly weird related to my own config, every so often the focused window "follows me" when I switch workspaces. but it keeps its tiled/float state
2023-04-19 22:56:04 +0200 <jabuxas> I can record what's happening if that helps
2023-04-19 22:56:44 +0200 <geekosaur> ewmhFullscreen is what listens for the app asking to be fullscreened (_NET_WM_STATE_FULLSCREEN message sent to the root window)
2023-04-19 22:57:06 +0200 <geekosaur> the other way it can happen is _NET_WM_STATE changes
2023-04-19 22:57:18 +0200 <geekosaur> but you have no _NET_WM_STATE at all
2023-04-19 22:58:08 +0200 <jabuxas> i maybe have a similar issue where on max layout, if i touch a floating window, the window being maxed behind the floated one switches with the other one hidden
2023-04-19 23:01:18 +0200 <jabuxas> https://imgur.com/a/MHg4ekp
2023-04-19 23:01:24 +0200 <geekosaur> that one is the infamous "bug 4", there are partial workarounds but no fix
2023-04-19 23:01:56 +0200 <jabuxas> oh you opened that one
2023-04-19 23:02:50 +0200 <geekosaur> not the bug 4 in the current tracker; the one in the old tracker that we couldn't migrate
2023-04-19 23:03:21 +0200 <geekosaur> https://code.google.com/archive/p/xmonad/issues/4
2023-04-19 23:04:33 +0200 <geekosaur> basically, focus is kept by rotating the StackSet, and while floats are on top of everything else they're spread throughout the StackSet so clicking on one rotates the whole StackSet
2023-04-19 23:05:45 +0200 <geekosaur> the StackSet is mathematically lovely but almost pathological UX
2023-04-19 23:08:48 +0200 <jabuxas> so fixing it would take a lot of work
2023-04-19 23:13:46 +0200hrberg(~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 276 seconds)
2023-04-19 23:13:58 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2023-04-19 23:20:11 +0200 <jabuxas> if you want to see the bug i uploaded to imgur https://imgur.com/a/mIUmaNU
2023-04-19 23:27:34 +0200 <geekosaur> that looks like it's unnmapping and remapping itself
2023-04-19 23:35:07 +0200L29Ah(~L29Ah@wikipedia/L29Ah) ()
2023-04-19 23:35:22 +0200 <geekosaur> well, re floating windows in general, we have https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Layout/FocusTracking.hs which I'm not sure is in a release yet, but you said you run git
2023-04-19 23:35:52 +0200 <geekosaur> but it's an imperfect solution
2023-04-19 23:44:56 +0200catman(~catman@user/catman)
2023-04-19 23:58:39 +0200L29Ah(~L29Ah@wikipedia/L29Ah)