| 2023-04-18 00:00:44 +0000 | <geekosaur> | (use race, thread 1 does threadDelay 5000000 and exits, thread 2 opens the display and records events and timestamps in the Chan) |
| 2023-04-18 00:01:23 +0000 | <geekosaur> | then the main thread harvests from the Chan and the timestamp of the last event read is when xmonad finished |
| 2023-04-18 00:03:11 +0000 | malook | (~Thunderbi@46.52.55.36) (Quit: malook) |
| 2023-04-18 00:04:17 +0000 | <JonathanWatson[m> | sounds good i'll give that a go |
| 2023-04-18 00:07:35 +0000 | <JonathanWatson[m> | <geekosaur> "(use race, thread 1 does..." <- although ideally thread 1 would restart the timer every time the Chan is posted to |
| 2023-04-18 00:08:18 +0000 | <geekosaur> | I wouldn't say so, a timeout of 5-10 seconds should be fine |
| 2023-04-18 00:08:29 +0000 | <JonathanWatson[m> | fair enough |
| 2023-04-18 00:08:41 +0000 | <JonathanWatson[m> | also since we only care about the last timeout wouldn't it be better to use an MVar? |
| 2023-04-18 00:08:46 +0000 | <geekosaur> | unless you're testing with 10000 windows in which case you will discover that the StackSet was a bit of a mistake 🙂 |
| 2023-04-18 00:09:04 +0000 | <geekosaur> | mm, probably |
| 2023-04-18 00:09:07 +0000 | <JonathanWatson[m> | well actually |
| 2023-04-18 00:09:26 +0000 | <geekosaur> | (the StackSet is backed by a pair of lists. large lists are slow |
| 2023-04-18 00:09:28 +0000 | <geekosaur> | ) |
| 2023-04-18 00:09:47 +0000 | <JonathanWatson[m> | that's a good point i'm more going for a small number of windows but lots of operations |
| 2023-04-18 00:11:06 +0000 | <JonathanWatson[m> | but ideally i would want the time to be nearer the 1 minute mark so its easier to see the differences when the program gets slower |
| 2023-04-18 00:11:21 +0000 | <JonathanWatson[m> | and i get nicer error bars |
| 2023-04-18 00:18:30 +0000 | catman | (~catman@user/catman) (Ping timeout: 255 seconds) |
| 2023-04-18 00:25:34 +0000 | hightower3 | (~hightower@213.149.61.95) (Read error: Connection reset by peer) |
| 2023-04-18 00:25:59 +0000 | hightower3 | (~hightower@213.149.61.95) |
| 2023-04-18 00:40:25 +0000 | ft | (~ft@i59F54987.versanet.de) (Ping timeout: 240 seconds) |
| 2023-04-18 00:42:23 +0000 | ft | (~ft@87.122.11.39) |
| 2023-04-18 00:53:58 +0000 | <JonathanWatson[m> | i've been stuck on this for a while... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/1e233b4267194150308a715065a48e7cc118…>) |
| 2023-04-18 00:54:24 +0000 | <JonathanWatson[m> | timeout 1000000 (takeMVar lastTimestampVar) doesn't seem to actually timeout |
| 2023-04-18 00:55:02 +0000 | <JonathanWatson[m> | i have to press alt+space before it actually decides to go down the Nothing branch |
| 2023-04-18 00:55:12 +0000 | <JonathanWatson[m> | * i've been stuck on this for a while... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9ed66cf078b16abf1bc4ff6f74d586a7ec26…>) |
| 2023-04-18 00:55:30 +0000 | <JonathanWatson[m> | which is very ood |
| 2023-04-18 00:55:40 +0000 | <JonathanWatson[m> | * which is very odd |
| 2023-04-18 00:56:06 +0000 | <JonathanWatson[m> | * i've been stuck on this for a while... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/f0b49a02c3153aa5faee4c1c6c4edbb360a9…>) |
| 2023-04-18 00:56:59 +0000 | <JonathanWatson[m> | this is despite the print t not doing anything after the benchmark |
| 2023-04-18 00:58:56 +0000 | <JonathanWatson[m> | i can only assume something to do with async |
| 2023-04-18 01:12:12 +0000 | <JonathanWatson[m> | ok i think `False -> return ()` was running too often |
| 2023-04-18 01:12:28 +0000 | <JonathanWatson[m> | and also i didn't put flush in it which is probably fine but it definitely needs a sleep |
| 2023-04-18 01:14:35 +0000 | <JonathanWatson[m> | well i have a benchmark now |
| 2023-04-18 01:14:44 +0000 | <JonathanWatson[m> | @geekosaur thank you so much for the help |
| 2023-04-18 01:14:45 +0000 | <lambdabot> | Unknown command, try @list |
| 2023-04-18 01:15:21 +0000 | catman | (~catman@user/catman) |
| 2023-04-18 02:08:25 +0000 | td_ | (~td@i53870920.versanet.de) (Ping timeout: 240 seconds) |
| 2023-04-18 02:10:31 +0000 | td_ | (~td@i53870902.versanet.de) |
| 2023-04-18 02:41:15 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
| 2023-04-18 02:44:17 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) |
| 2023-04-18 04:51:00 +0000 | catman | (~catman@user/catman) (Quit: WeeChat 3.8) |
| 2023-04-18 05:00:14 +0000 | catman | (~catman@user/catman) |
| 2023-04-18 05:38:25 +0000 | catman | (~catman@user/catman) (Ping timeout: 240 seconds) |
| 2023-04-18 06:37:04 +0000 | catman | (~catman@user/catman) |
| 2023-04-18 06:38:49 +0000 | mncheck | (~mncheck@193.224.205.254) |
| 2023-04-18 06:55:27 +0000 | ft | (~ft@87.122.11.39) (Quit: leaving) |
| 2023-04-18 07:23:14 +0000 | catman | (~catman@user/catman) (Ping timeout: 246 seconds) |
| 2023-04-18 07:28:55 +0000 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-04-18 08:03:40 +0000 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-04-18 08:24:58 +0000 | Miroboru | (~myrvoll@188.124.159.94) |
| 2023-04-18 08:25:49 +0000 | <Miroboru> | Is there any way to reset the layout to a default setting in xmonad? |
| 2023-04-18 08:26:34 +0000 | <Miroboru> | Googling this I see that mod-shift-space should do this, but in my case this just prints space |
| 2023-04-18 08:31:12 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2023-04-18 08:49:15 +0000 | lykos153 | (~lykos153@2001:470:69fc:105::c8ea) |
| 2023-04-18 09:00:26 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-04-18 09:00:26 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-04-18 09:01:23 +0000 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-04-18 10:01:29 +0000 | hightower4 | (~hightower@213.149.61.245) |
| 2023-04-18 10:04:31 +0000 | hightower3 | (~hightower@213.149.61.95) (Ping timeout: 276 seconds) |
| 2023-04-18 11:43:16 +0000 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) |
| 2023-04-18 12:40:48 +0000 | <geekosaur> | Miroboru, that sounds like your config has it rebound |
| 2023-04-18 12:41:00 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2023-04-18 12:41:17 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-04-18 12:41:26 +0000 | <geekosaur> | you want to bind a key to `asks (layoutHook . config) >>= setLayout` |
| 2023-04-18 12:42:00 +0000 | <geekosaur> | JonathanWatson[m, sorry, I'd gone to bed |
| 2023-04-18 13:06:45 +0000 | hightower4 | (~hightower@213.149.61.245) (Ping timeout: 240 seconds) |
| 2023-04-18 13:27:31 +0000 | <Miroboru> | geekosaur: Yeah, the issue was it not being bound. I still cannot find anything that does what I want though. |
| 2023-04-18 13:30:22 +0000 | <Miroboru> | What I basically want is something that resets the sizes of the windows when called. |
| 2023-04-18 13:33:10 +0000 | <geekosaur> | what layout are you using? |
| 2023-04-18 13:34:31 +0000 | <geekosaur> | some layouts use the original requested size of the window, but don't save that, nor does the application, so you can't go back |
| 2023-04-18 14:02:44 +0000 | <geekosaur> | that said, a layout like Tall should completely reset on `setLayout` |
| 2023-04-18 14:11:06 +0000 | <geekosaur> | oh, you need to `setLayout` on each workspace, there's no switch that applies to all workspaces (but I feel like there's a function that applies something to all workspaces, I can't recall it though) |
| 2023-04-18 15:13:31 +0000 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.8) |
| 2023-04-18 15:47:25 +0000 | mc47 | (~mc47@xmonad/TheMC47) (Ping timeout: 252 seconds) |
| 2023-04-18 15:48:48 +0000 | hightower2 | (~hightower@230-130.dsl.iskon.hr) |
| 2023-04-18 16:00:05 +0000 | Solid[m] | (~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle) |
| 2023-04-18 16:00:14 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-04-18 16:00:14 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-04-18 16:14:46 +0000 | berberman | (~berberman@user/berberman) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2023-04-18 16:15:07 +0000 | berberman | (~berberman@user/berberman) |
| 2023-04-18 16:27:34 +0000 | thunderrd | (~thunderrd@183.182.111.241) |
| 2023-04-18 16:32:00 +0000 | thunderrd | (~thunderrd@183.182.111.241) (Remote host closed the connection) |
| 2023-04-18 16:43:42 +0000 | fcser | (~fcser@booty.farted.net) (Excess Flood) |
| 2023-04-18 16:43:49 +0000 | fcser | (~fcser@booty.farted.net) |
| 2023-04-18 16:53:31 +0000 | werneta | (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection) |
| 2023-04-18 17:27:00 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
| 2023-04-18 17:29:58 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) |
| 2023-04-18 17:34:40 +0000 | hightower2 | (~hightower@230-130.dsl.iskon.hr) (Ping timeout: 252 seconds) |
| 2023-04-18 18:32:37 +0000 | catman | (~catman@user/catman) |
| 2023-04-18 19:14:59 +0000 | hightower2 | (~hightower@230-130.dsl.iskon.hr) |
| 2023-04-18 19:35:50 +0000 | catman | (~catman@user/catman) (Ping timeout: 246 seconds) |
| 2023-04-18 20:36:00 +0000 | catman | (~catman@user/catman) |
| 2023-04-18 20:42:08 +0000 | catman | (~catman@user/catman) (Ping timeout: 248 seconds) |
| 2023-04-18 20:56:02 +0000 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) |
| 2023-04-18 21:58:25 +0000 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) (Ping timeout: 240 seconds) |
| 2023-04-18 22:07:12 +0000 | pharonix71 | (~pharonix7@user/pharonix71) (Remote host closed the connection) |
| 2023-04-18 22:07:53 +0000 | <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-18 22:07:55 +0000 | <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-18 22:07:57 +0000 | <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-18 22:08:07 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2023-04-18 22:08:19 +0000 | Solid[m] | (~slot-matr@2001:470:69fc:105::1:a84) |
| 2023-04-18 22:08:34 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-04-18 22:09:10 +0000 | <jabuxas> | i tried looking at source code but couldn't find the exact reason for why that happened with my skills |
| 2023-04-18 22:09:21 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
| 2023-04-18 22:32:05 +0000 | jabuxas | (~jabuxas@user/jabuxas) (Ping timeout: 260 seconds) |
| 2023-04-18 22:34:23 +0000 | <geekosaur> | I have no idea what to do about an xlib crash… |
| 2023-04-18 22:34:36 +0000 | <geekosaur> | switching to xcb isn't really an option at this point |
| 2023-04-18 22:35:30 +0000 | catman | (~catman@user/catman) |
| 2023-04-18 22:39:02 +0000 | <L29Ah> | fix xlib |
| 2023-04-18 22:39:14 +0000 | <L29Ah> | are you sure it's xlib tho? |
| 2023-04-18 22:41:37 +0000 | <geekosaur> | it's the only place that can produce that error |
| 2023-04-18 22:42:14 +0000 | <geekosaur> | we don't make poly calls, which is the only other thing that can produce that error |
| 2023-04-18 22:46:22 +0000 | <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-18 22:48:59 +0000 | <L29Ah> | alternatively someone could fix https://github.com/qutebrowser/qutebrowser/issues/5108 and then we can pretend like xmonad has no bugs |
| 2023-04-18 22:49:14 +0000 | <L29Ah> | geekosaur: https://gitlab.freedesktop.org/xorg/lib/libx11/-/commits/master too many fresh commits for that hypothesis |
| 2023-04-18 22:49:46 +0000 | <L29Ah> | also, why is it only triggered by Tabbed? |
| 2023-04-18 22:50:02 +0000 | <L29Ah> | i'd expect things like my huge window matching rules look up WM_NAME as well |
| 2023-04-18 22:52:53 +0000 | <geekosaur> | do they use `title`? |
| 2023-04-18 22:53:04 +0000 | <geekosaur> | (it's usually a bad idea, especially for browsers) |
| 2023-04-18 22:54:01 +0000 | <L29Ah> | geekosaur: https://github.com/l29ah/xmonad-config/blob/master/xmonad.hs#L260 |
| 2023-04-18 22:55:05 +0000 | <geekosaur> | it's in a composeOne and thereby skipped because https://github.com/l29ah/xmonad-config/blob/master/xmonad.hs#L253 matched |
| 2023-04-18 22:59:06 +0000 | <L29Ah> | i wonder why xmonad doesn't crash when qutebrowser is already running |
| 2023-04-18 23:00:03 +0000 | <L29Ah> | i can restart xmonad after crashing and it's fine with its Tabbed qutebrowser |
| 2023-04-18 23:11:23 +0000 | mncheck | (~mncheck@193.224.205.254) (Ping timeout: 246 seconds) |
| 2023-04-18 23:11:54 +0000 | <geekosaur> | https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Util/NamedWindows.hs#L52-L53 from updateDeco |
| 2023-04-18 23:12:18 +0000 | <geekosaur> | which is called when the tab is created and probably not again until you do something that resizes the tab |
| 2023-04-18 23:12:51 +0000 | <L29Ah> | but a tab is created each time xmonad is restarted |
| 2023-04-18 23:13:05 +0000 | <L29Ah> | s/rest/st/ |
| 2023-04-18 23:13:06 +0000 | <geekosaur> | created, or left around? |
| 2023-04-18 23:13:46 +0000 | <L29Ah> | geekosaur: what do you mean "left around"? xmonad needs to create all them decorations when it starts up |
| 2023-04-18 23:21:23 +0000 | <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-18 23:21:46 +0000 | <geekosaur> | (I'm testing stuff in my sandbox as I go;p the tabs definitely disappear before xmonad restarts) |
| 2023-04-18 23:23:08 +0000 | <L29Ah> | ok, xprop says the WM_NAME is much smaller |
| 2023-04-18 23:23:21 +0000 | <L29Ah> | maybe qutebrowser dumps the huge one and then trims it afterwards, idk |
| 2023-04-18 23:24:23 +0000 | <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-18 23:25:01 +0000 | <L29Ah> | if it tried to render it, then it fetched it |
| 2023-04-18 23:25:24 +0000 | <geekosaur> | yeh |
| 2023-04-18 23:25:51 +0000 | <geekosaur> | also I note that qutebrowser is trying to render the string at first and then the render thread crashes |
| 2023-04-18 23:26:12 +0000 | <geekosaur> | which is why it's not happening on restart; the tab has an error string instead |
| 2023-04-18 23:29:15 +0000 | <L29Ah> | > the render thread crashes |
| 2023-04-18 23:29:16 +0000 | <L29Ah> | does it? i think the URL itself is about the render thread crashing |
| 2023-04-18 23:29:17 +0000 | <lambdabot> | error: |
| 2023-04-18 23:29:17 +0000 | <lambdabot> | Variable not in scope: the :: (Doc -> String) -> t0 -> t1 -> terror: |
| 2023-04-18 23:29:17 +0000 | <lambdabot> | • Variable not in scope: thread |
| 2023-04-18 23:29:32 +0000 | <L29Ah> | so you might be confusing it |
| 2023-04-18 23:30:10 +0000 | <geekosaur> | only if it's a quine; look at the url it claims to be opening |
| 2023-04-18 23:30:14 +0000 | <L29Ah> | and xprop is showing a trimmed version of the URL that is yanked with yy |
| 2023-04-18 23:30:32 +0000 | <L29Ah> | the one that gets yanked is huge |
| 2023-04-18 23:32:36 +0000 | <geekosaur> | yes, and includes: Error while opening https://blueprint.bryanjohnson.co.uk… |
| 2023-04-18 23:32:43 +0000 | <L29Ah> | found where the qutebrowser title is set, but no idea why is it trimmed |
| 2023-04-18 23:32:45 +0000 | <L29Ah> | // self.widget.window().setWindowTitle(title) |
| 2023-04-18 23:35:30 +0000 | <geekosaur> | damn, maybe this thing is a quine |
| 2023-04-18 23:36:00 +0000 | <geekosaur> | but still, that means it starts out showing the url and then changes it to the page title |
| 2023-04-18 23:36:26 +0000 | <geekosaur> | so it's still shoveled 389k into WM_NAME and/or _NET_WM_NAME |
| 2023-04-18 23:41:03 +0000 | <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-18 23:41:30 +0000 | <geekosaur> | and does not crash |
| 2023-04-18 23:43:42 +0000 | <geekosaur> | hm, it's a bit late for liskin to be around but… around? |
| 2023-04-18 23:49:47 +0000 | <liskin> | About to fall asleep |
| 2023-04-18 23:51:48 +0000 | <geekosaur> | oh. check back here tomorrow then |
| 2023-04-18 23:52:05 +0000 | <L29Ah> | i brainfarted at https://github.com/qutebrowser/qutebrowser/issues/5108 now gotta go sleep as well |
| 2023-04-18 23:52:07 +0000 | <geekosaur> | I'm trying to gdb to verify where we're crashing but I think it's Xlib |