2023/04/20

2023-04-20 00:11:01 +0200 <jabuxas> how would i implement that?
2023-04-20 00:17:51 +0200 <geekosaur> https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Layout/FocusTracking.hs#L41-L60
2023-04-20 00:17:52 +0200 <liskin> Well that PR of mine lets you disable ewmh fullscreen for individual apps
2023-04-20 00:18:06 +0200 <liskin> So that might be a viable workaround
2023-04-20 00:20:12 +0200 <geekosaur> I'm looking over your config (that dbus stuff looks familiar πŸ™‚ )
2023-04-20 00:21:11 +0200 <geekosaur> looks like you'd change line 394: wrap what you have in parentheses and put `focusTracking` in front of it
2023-04-20 00:21:39 +0200 <geekosaur> after importing XMonad.Layout.FocusTracking
2023-04-20 00:23:41 +0200 <jabuxas> doesn't seem to do anything, should i restart X completely?
2023-04-20 00:24:01 +0200 <jabuxas> `focusTracking (tiled ||| simpleFloat ||| Mirror tiled ||| Full)`
2023-04-20 00:24:08 +0200 <geekosaur> it will only do something with floats
2023-04-20 00:24:33 +0200 <geekosaur> it tries to remember and restore where you were when you select the tiled layer
2023-04-20 00:24:57 +0200 <geekosaur> to work around that StackSet rotation issue I mentioned earlier
2023-04-20 00:25:03 +0200 <geekosaur> ("bug 4")
2023-04-20 00:25:20 +0200mncheck(~mncheck@193.224.205.254) (Ping timeout: 260 seconds)
2023-04-20 00:25:23 +0200 <jabuxas> ohhhhhhh i thought we were talking about the other bug
2023-04-20 00:25:25 +0200 <jabuxas> my bad
2023-04-20 00:25:37 +0200 <geekosaur> nope, I think you need liskin for that
2023-04-20 00:25:57 +0200 <jabuxas> yeah now floats aren't changing the max layout, nice :)
2023-04-20 00:26:07 +0200 <geekosaur> and I still suspect the _NET_WM_STATE thing is part of the problem
2023-04-20 00:26:45 +0200 <jabuxas> interestingly even though it doesn't change on moving or even interacting, it changes when closing the float
2023-04-20 00:29:09 +0200 <jabuxas> liskin: are you able to help with that issue?
2023-04-20 00:29:50 +0200 <geekosaur> [19 22:17:52] <liskin> Well that PR of mine lets you disable ewmh fullscreen for individual apps
2023-04-20 00:29:50 +0200 <geekosaur> [19 22:18:06] <liskin> So that might be a viable workaround
2023-04-20 00:30:17 +0200 <geekosaur> if all else fails you can disable fullscreen just for those apps and let it work for the ones it works with
2023-04-20 00:31:09 +0200 <geekosaur> but I really think it moving itself to +0+0 means it's unmapping and remapping, without the FULLSCREEN atom set so it doesn't go fullscreen
2023-04-20 00:31:19 +0200 <jabuxas> oh that's what he was talking about, that's why i was confused. ok.
2023-04-20 00:31:39 +0200 <jabuxas> i'll try that pr, let me see how i would use that
2023-04-20 00:31:54 +0200 <geekosaur> I thought you were already on that commit?
2023-04-20 00:32:02 +0200 <geekosaur> (it's already merged)
2023-04-20 00:32:07 +0200 <jabuxas> i'm on the commit, i don't know how to use ToggleFullFloat
2023-04-20 00:32:26 +0200 <geekosaur> [19 19:39:15] <geekosaur> %gitcontrib 673de11ca87
2023-04-20 00:32:27 +0200 <geekosaur> [19 19:39:16] <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-20 00:34:28 +0200 <jabuxas> doFullFloatSave
2023-04-20 00:34:31 +0200 <jabuxas> is that a managehook option?
2023-04-20 00:36:06 +0200 <geekosaur> yes
2023-04-20 00:36:29 +0200 <geekosaur> it makes a fullscreen window while saving its original state
2023-04-20 00:37:14 +0200 <geekosaur> but I'm not sure that's what you need here, it's not that its original state is lost, it looks like it's putting itself into a new floating non-fullscreen window
2023-04-20 00:38:41 +0200 <geekosaur> tbh I'm quite confused by what that video showed
2023-04-20 00:39:30 +0200 <geekosaur> but it is possible that all you need is a ManageHook that matches it and fullscreens it
2023-04-20 00:39:51 +0200 <jabuxas> why fullscreen it?
2023-04-20 00:39:58 +0200 <geekosaur> but I'm worried that will just lead to a map/unmap loop
2023-04-20 00:40:15 +0200 <geekosaur> isn't that what you wanted? it's un-fullscreening itself
2023-04-20 00:40:29 +0200 <geekosaur> so you would re-fullscreen it
2023-04-20 00:40:49 +0200 <jabuxas> the problem is that it tiles itself when it should be floating.. isn't it?
2023-04-20 00:40:52 +0200 <jabuxas> at least that's how i'm viewing it
2023-04-20 00:41:31 +0200 <geekosaur> that didn't look tiled, it looked floated at +0+0
2023-04-20 00:41:41 +0200 <geekosaur> with a non-fullscreen window
2023-04-20 00:42:33 +0200 <geekosaur> which is a thing that used to happen with old apps, that didn't distinguish between program-defined/default and user-defined position
2023-04-20 00:42:53 +0200 <geekosaur> (which is what's weird because that's an X11R3 issue)
2023-04-20 00:43:55 +0200 <jabuxas> i'll re-record it brb
2023-04-20 00:46:01 +0200 <geekosaur> but even if it is tiling itself, that still requires an unmap/remap and you need a ManageHook to make it do the right thing
2023-04-20 00:47:25 +0200rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) (Ping timeout: 240 seconds)
2023-04-20 00:47:46 +0200 <geekosaur> (applications know nothing about float vs. tiled, that's an internal xmonad thing)
2023-04-20 00:48:19 +0200 <jabuxas> i do think it's remapping itself then, is there a way to check its state and force float on it every time?
2023-04-20 00:49:02 +0200 <geekosaur> that's what the ManageHook is for
2023-04-20 00:52:16 +0200 <jabuxas> but isn't it already set? doCenterFloat
2023-04-20 00:53:28 +0200 <geekosaur> doFullFloat?
2023-04-20 00:53:57 +0200 <geekosaur> but apparently it's not matching the window that gets remapped because that is not centered
2023-04-20 00:54:21 +0200 <jabuxas> https://imgur.com/a/7bWUw1t here is re-recorded, showing that it suddenly tiles itself
2023-04-20 00:54:37 +0200 <geekosaur> when it relocates itself to +0+0 / "tiles itself" / whatever, try to get its properties
2023-04-20 00:54:47 +0200 <jabuxas> ok
2023-04-20 00:55:53 +0200 <geekosaur> yeh, that's tiled
2023-04-20 00:56:07 +0200 <geekosaur> a client wouldn't know how to do that itself, it would have to unmap and remap
2023-04-20 00:56:31 +0200 <geekosaur> and since there'[s no _NET_WM_STATE the isFullscreen rule doesn't fire
2023-04-20 00:56:51 +0200 <geekosaur> so… why doesn't the other one fire?
2023-04-20 00:57:06 +0200 <geekosaur> which is why I want to see what props it has after it does that
2023-04-20 00:58:16 +0200 <jabuxas> https://dpaste.org/Brocp
2023-04-20 01:00:00 +0200 <jabuxas> it didnt change anything did it
2023-04-20 01:11:02 +0200 <geekosaur> WM_CLASS is gone so the ManageHook won't match it
2023-04-20 01:11:31 +0200 <geekosaur> unless you missed copying it and the second one ends at WM_LOCALE)NAME
2023-04-20 01:11:38 +0200 <geekosaur> WM_LOCALE_NAME
2023-04-20 01:11:53 +0200 <jabuxas> i'll check again
2023-04-20 01:11:56 +0200 <jabuxas> but i think you're right lmao
2023-04-20 01:11:57 +0200 <jabuxas> how does it not have a class
2023-04-20 01:12:23 +0200 <jabuxas> have you ever seen that before?
2023-04-20 01:13:12 +0200 <geekosaur> WM_NORMAL_HINTS is completely different
2023-04-20 01:13:29 +0200 <geekosaur> yes, there are broken programs that don't set it
2023-04-20 01:14:27 +0200 <geekosaur> notably it sets min and max size the same, so it should be autofloated at its requested size
2023-04-20 01:14:36 +0200 <jabuxas> i did an oopsie, it does set class https://dpaste.org/QUiA8
2023-04-20 01:14:52 +0200 <geekosaur> initially it's 1600x900, afterward it's 1912x1047
2023-04-20 01:15:07 +0200 <geekosaur> so it is withdrawing and remapping
2023-04-20 01:16:34 +0200 <geekosaur> but why isn't it being matched, then?
2023-04-20 01:17:02 +0200 <jabuxas> question of the century
2023-04-20 01:17:51 +0200 <geekosaur> hm, or it's resizing and updating WM_NORMAL_HINTS without remapping (a no-no; wms only read it on map)
2023-04-20 01:18:44 +0200 <geekosaur> almost tempted to have you dump events, but that produces a _lot_ of crap
2023-04-20 01:19:28 +0200 <geekosaur> (X.H.DebugEvents)
2023-04-20 01:21:39 +0200 <jabuxas> how is it used? documentation isn't saying
2023-04-20 01:23:57 +0200 <geekosaur> oh, right, I didn't document that because it's not really an end user thing, it's a diagnostic tool
2023-04-20 01:24:04 +0200 <jabuxas> do I add it like `main = xmonad $ … . debugEventsHook` ?
2023-04-20 01:24:13 +0200 <geekosaur> handleEventHook = debugEventsHook
2023-04-20 01:24:32 +0200 <geekosaur> (along with manageHook, logHook, layoutHook, etc.)
2023-04-20 01:24:49 +0200 <jabuxas> can i <> it?
2023-04-20 01:25:24 +0200 <geekosaur> yes
2023-04-20 01:25:39 +0200 <jabuxas> where does it go to? the log
2023-04-20 01:25:42 +0200 <geekosaur> you can <> everything except the layoutHook
2023-04-20 01:25:45 +0200 <geekosaur> yes
2023-04-20 01:25:54 +0200 <geekosaur> so you'll need to figure out where the session log is
2023-04-20 01:26:08 +0200 <geekosaur> how do you start your session?
2023-04-20 01:26:14 +0200 <jabuxas> xinit
2023-04-20 01:26:37 +0200 <geekosaur> oh. you'll need to restart it, redirecting xinit's output to a file
2023-04-20 01:26:50 +0200 <jabuxas> `exec xmonad | tee ~/.config/xmonad/xmonad.log`
2023-04-20 01:26:54 +0200 <jabuxas> that's how i start it
2023-04-20 01:27:19 +0200 <geekosaur> exec isn't doing you any good there
2023-04-20 01:27:33 +0200 <jabuxas> that's inside .xinitrc
2023-04-20 01:27:36 +0200 <geekosaur> in that case though you should see the events in xmonad.log
2023-04-20 01:28:33 +0200 <jabuxas> i'll restart either way because it's not writing anything to that file
2023-04-20 01:28:45 +0200 <jabuxas> at least not any of the logs you're waiting for
2023-04-20 01:28:56 +0200 <jabuxas> just what was there before
2023-04-20 01:30:56 +0200 <geekosaur> well, "spew" was relatoive. xmonad spends most of its time waiting for window manager events such as windows opening/closing and such
2023-04-20 01:31:34 +0200 <geekosaur> and you really don;t want it responding to a lot of stuff, mostly it should stay out of the way
2023-04-20 01:32:08 +0200 <jabuxas> it just has normal logs that normally appear there from apps https://bpa.st/AAKAO
2023-04-20 01:32:36 +0200 <jabuxas> handleEventHook = -- Hacks.windowedFullscreenFixEventHook swallowEventHook (className =? "Alacritty" <||> className =? "kitty" <||> className =? "XTerm") (return True) <> Hacks.trayerPaddingXmobarEventHook <> debugEventsHook <> myEventHook,
2023-04-20 01:32:58 +0200 <jabuxas> the tabs messed it up
2023-04-20 01:33:24 +0200 <geekosaur> and lack of newlines. this isn't matrix or discord
2023-04-20 01:34:10 +0200 <jabuxas> still figuring out how to properly do things in weechat
2023-04-20 01:35:12 +0200 <geekosaur> it's best not to paste code directly into irc at all
2023-04-20 01:35:40 +0200 <geekosaur> it'll get mangled, it'll get interrupted by join/part messages, it'll be generally annoying
2023-04-20 01:36:10 +0200 <jabuxas> oh yeah, now i got the log
2023-04-20 01:36:24 +0200 <jabuxas> needed to `startx > ~/.Xlog 2>&1`
2023-04-20 01:36:32 +0200 <jabuxas> i'll start the game now
2023-04-20 01:42:26 +0200 <jabuxas> https://0x0.st/H8I1.txt
2023-04-20 01:45:06 +0200 <geekosaur> hm, I have some bugs I need to fix πŸ˜•
2023-04-20 01:46:07 +0200 <jabuxas> this is perhaps another more complete one https://0x0.st/H8Ij.txt -- i didn't auto-login into game this time around
2023-04-20 01:46:45 +0200 <jabuxas> geekosaur: ok, ty for all the help, i'll still be here in case someone finds out anything. i could look into this log for weeks and I wouldn't find the culprit lol
2023-04-20 01:50:43 +0200 <geekosaur> there's some weird stuff in here. it seems to be setting _NET_WM_STATE via a client message, which is completely wrong; it's a window property
2023-04-20 01:57:12 +0200 <geekosaur> I think I caught it unmapping, remapping, then setting the mandatory properties
2023-04-20 01:57:18 +0200 <geekosaur> wrong order
2023-04-20 02:16:27 +0200 <geekosaur> I am somewhat tempted to have you try debugManageHookOn (https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L56) and then do what makes it tile, and see if the ManageHook triggers and if it has sane window information
2023-04-20 03:57:20 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-20 04:06:37 +0200td_(~td@i5387091D.versanet.de) (Ping timeout: 252 seconds)
2023-04-20 04:08:15 +0200td_(~td@i53870923.versanet.de)
2023-04-20 05:36:30 +0200catman(~catman@user/catman) (Ping timeout: 255 seconds)
2023-04-20 06:32:44 +0200catman(~catman@user/catman)
2023-04-20 07:36:45 +0200catman(~catman@user/catman) (Ping timeout: 240 seconds)
2023-04-20 09:09:34 +0200mncheck(~mncheck@193.224.205.254)
2023-04-20 09:29:43 +0200mc47(~mc47@xmonad/TheMC47)
2023-04-20 09:36:31 +0200 <liskin> I'm a bit overstretched these days :-(
2023-04-20 09:36:46 +0200 <liskin> Only ircing from toilets and stuff
2023-04-20 09:39:30 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 255 seconds)
2023-04-20 09:41:12 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-20 09:50:51 +0200 <mc47> liskin, geekosaur, Solid: should we plan how to merge [Leary]'s work (the mvdt stuff) to core? It makes `windows` way more intuitive (#807 was a breeze after their changes) and I think it's an improvement
2023-04-20 09:56:45 +0200 <geekosaur> I think the current plan is to release the next version as 1.0 and then merge it, because it's a pretty breaking change
2023-04-20 10:00:57 +0200 <liskin> how much of xmonad-contrib does it break, if any?
2023-04-20 10:02:00 +0200 <geekosaur> I'm more worried about configs. I know I've handed out various invocations of `windows` with wild abandon and am rather worried that they'll all have to be modified
2023-04-20 10:02:52 +0200 <geekosaur> `windows` is pretty core, after all
2023-04-20 10:03:18 +0200 <liskin> yeah, people will hate us for this :-/
2023-04-20 10:04:01 +0200 <geekosaur> that's why I want this to be 1.1 πŸ™‚
2023-04-20 10:04:06 +0200 <mc47> I mean, they can just _not_ upgrade, right?
2023-04-20 10:05:15 +0200 <liskin> they'd first need to know not to upgrade
2023-04-20 10:05:42 +0200 <liskin> if we break configs of dozens of people they'll be upset
2023-04-20 10:05:46 +0200 <liskin> that's inevitable :-)
2023-04-20 10:06:07 +0200 <geekosaur> hell, we did that just with deprecations
2023-04-20 10:07:11 +0200 <liskin> (if I was in their place I'd probably tweet something like "why the fuck do these morons waste time breaking user configs by core refactors instead of biting the bullet and just dealing with Wayland alread?" :-))
2023-04-20 10:07:29 +0200 <geekosaur> they already do that πŸ™‚
2023-04-20 10:07:41 +0200 <liskin> :-))
2023-04-20 10:08:16 +0200 <mc47> Oh right, we can't really deprecate
2023-04-20 10:08:29 +0200 <[Leary]> The ManageHook PR, which I'll stress /doesn't actually need to go in/, will break basically every config. The core PR #432 (and most if not all of the others), however, break virtually nothing; only the repeatable action stuff (which can be fixed contrib-side).
2023-04-20 10:09:08 +0200 <[Leary]> Sorry for not getting back to working on this stuff, by the way. My motivation has been elsewhere.
2023-04-20 10:09:26 +0200 <mc47> I mean... we could just deprecate windows and introduce another combinator with the same implementation
2023-04-20 10:09:38 +0200 <mc47> Might be better than just a silent breaking change
2023-04-20 10:09:44 +0200 <geekosaur> yeh, I was focused elsewhere for a while too
2023-04-20 10:10:03 +0200 <geekosaur> spent today on a bunch of xmonad issues to catch up
2023-04-20 10:10:08 +0200 <mc47> No need to say sorry, it's great that you contribute code in the first place :D
2023-04-20 10:10:14 +0200 <liskin> mc47: contrib invokes windows in like a million of places :-)
2023-04-20 10:10:25 +0200 <liskin> I don't think you can realistically keep both impls in
2023-04-20 10:10:40 +0200 <mc47> right..
2023-04-20 10:10:43 +0200 <geekosaur> inevitably since it's pretty much the heart of xmonad
2023-04-20 10:11:03 +0200 <[Leary]> The beauty of #432 is that we don't need to mess with `windows`, because the semantics haven't actually changed, and it's still used the same way.
2023-04-20 10:11:24 +0200 <geekosaur> oh, hm. maybe we can pull this off after all then
2023-04-20 10:11:34 +0200 <[Leary]> Only the implementation and (operational) interpretation change.
2023-04-20 10:11:38 +0200mc47has also been busy... planning a wedding :D
2023-04-20 10:12:09 +0200 <mc47> I think the problematic change is with the manageHook
2023-04-20 10:12:09 +0200 <geekosaur> congratulations?
2023-04-20 10:12:46 +0200 <mc47> yeah thanks
2023-04-20 10:13:21 +0200 <mc47> The rest of the changes probably won't break anything
2023-04-20 10:14:55 +0200 <liskin> well anyway, we can merge my floatLocation PR (needs changelog update), release 0.18 or 0.17.3, and then merge the non-managehook PRs and see what breaks
2023-04-20 10:15:02 +0200 <liskin> if we do a bit of messaging about it…
2023-04-20 10:15:34 +0200 <liskin> (I haven't seen the diffs yet though, sorry for that, had to prioritise other things in life lately)
2023-04-20 10:19:32 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de) (Quit: leaving)
2023-04-20 10:24:44 +0200 <mc47> I've been running #433 without any problems for quite some time
2023-04-20 10:24:50 +0200 <mc47> sounds like a plan :+1:
2023-04-20 10:38:54 +0200mc47(~mc47@xmonad/TheMC47) (Read error: Connection reset by peer)
2023-04-20 11:00:08 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle)
2023-04-20 11:00:08 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-04-20 11:00:08 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-20 11:01:40 +0200Miroboru(~myrvoll@188.124.159.94) (Quit: Lost terminal)
2023-04-20 12:53:31 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 240 seconds)
2023-04-20 12:55:37 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-20 13:24:56 +0200 <jabuxas> hello
2023-04-20 13:25:09 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-20 13:25:21 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2023-04-20 13:25:35 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-20 13:54:15 +0200Retropikzel[m](~retropikz@2001:470:69fc:105::14e7) ()
2023-04-20 14:25:12 +0200zawaken(~zawaken@user/zawaken) (Quit: ZNC - https://znc.in)
2023-04-20 14:25:47 +0200zawaken(~zawaken@user/zawaken)
2023-04-20 16:42:18 +0200mesaoptimizer(apotheosis@user/PapuaHardyNet)
2023-04-20 16:42:31 +0200mesaoptimizer(apotheosis@user/PapuaHardyNet) (Client Quit)
2023-04-20 17:28:57 +0200catman(~catman@user/catman)
2023-04-20 17:35:44 +0200catman(~catman@user/catman) (Remote host closed the connection)
2023-04-20 18:00:08 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-20 18:00:08 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle)
2023-04-20 18:00:08 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-04-20 18:08:55 +0200catman(~catman@user/catman)
2023-04-20 18:20:45 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-04-20 18:31:58 +0200jedimahdi[m](~jedimahdi@2001:470:69fc:105::3:49bf)
2023-04-20 18:34:58 +0200hrberg(~quassel@171.79-160-161.customer.lyse.net)
2023-04-20 18:46:43 +0200catman(~catman@user/catman) (Remote host closed the connection)
2023-04-20 18:53:29 +0200malook(~Thunderbi@2a02:9b0:404d:2c48:f80a:959:790e:cc21)
2023-04-20 18:54:45 +0200malook(~Thunderbi@2a02:9b0:404d:2c48:f80a:959:790e:cc21) ()
2023-04-20 19:09:19 +0200catman(~catman@user/catman)
2023-04-20 19:37:27 +0200catman(~catman@user/catman) (Remote host closed the connection)
2023-04-20 19:40:10 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2023-04-20 19:43:17 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2023-04-20 20:02:47 +0200catman(~catman@user/catman)
2023-04-20 20:12:31 +0200catman(~catman@user/catman) (Ping timeout: 256 seconds)
2023-04-20 20:23:31 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de)
2023-04-20 21:13:13 +0200catman(~catman@user/catman)
2023-04-20 21:15:02 +0200catman(~catman@user/catman) (Remote host closed the connection)
2023-04-20 21:47:17 +0200catman(~catman@user/catman)
2023-04-20 22:03:07 +0200catman(~catman@user/catman) (Remote host closed the connection)
2023-04-20 22:13:00 +0200 <jabuxas> one thing i managed to find out in the logs is when it "tiles" from 1600x900 floated state - https://bpa.st/6SLDC
2023-04-20 22:13:03 +0200 <jabuxas> i hope that helps with anything
2023-04-20 22:13:14 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-20 22:13:25 +0200Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2023-04-20 22:13:38 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-20 22:14:37 +0200 <geekosaur> yeh, that's requesting a resize
2023-04-20 22:38:25 +0200jabuxas(~jabuxas@user/jabuxas) (Ping timeout: 240 seconds)
2023-04-20 23:17:04 +0200 <geekosaur> hm, do we deal with a window requesting a resize via ConfigureRequest?
2023-04-20 23:17:33 +0200 <geekosaur> as distinct from either unmap/remap or the EWMH root window message?
2023-04-20 23:17:50 +0200 <geekosaur> (which I think we don't even advertise much less support)
2023-04-20 23:56:45 +0200jabuxas(~jabuxas@user/jabuxas)