| 2023-04-19 00:00:16 +0000 | <geekosaur> | argh. gdb is stuck at "reading symbols" |
| 2023-04-19 00:09:46 +0000 | <geekosaur> | I'll let it run overnight, hopefully I can get something halfway useful out of it tomorrow |
| 2023-04-19 00:57:18 +0000 | <geekosaur> | it's not even using cpu 😞 |
| 2023-04-19 01:00:09 +0000 | <geekosaur> | wtf, SIGTTOU. it's attached to a terminal… |
| 2023-04-19 01:18:00 +0000 | <geekosaur> | I attached to it from outside instead. and it doesn't crash |
| 2023-04-19 01:18:13 +0000 | <geekosaur> | I hate these kinds of bugs… |
| 2023-04-19 01:19:27 +0000 | <geekosaur> | and the tab is completely empty |
| 2023-04-19 01:20:04 +0000 | <geekosaur> | it's 2130, I'm going to bed and will try to sort this tomorrow |
| 2023-04-19 01:43:42 +0000 | hightower3 | (~hightower@213.202.92.246) |
| 2023-04-19 01:46:05 +0000 | hightower2 | (~hightower@230-130.dsl.iskon.hr) (Ping timeout: 240 seconds) |
| 2023-04-19 02:07:24 +0000 | td_ | (~td@i53870902.versanet.de) (Ping timeout: 255 seconds) |
| 2023-04-19 02:09:15 +0000 | td_ | (~td@i5387091D.versanet.de) |
| 2023-04-19 04:09:25 +0000 | catman | (~catman@user/catman) (Ping timeout: 240 seconds) |
| 2023-04-19 04:50:25 +0000 | piele | (~piele@tbonesteak.creativeserver.net) (Remote host closed the connection) |
| 2023-04-19 04:51:37 +0000 | piele | (~piele@tbonesteak.creativeserver.net) |
| 2023-04-19 06:28:23 +0000 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) (Ping timeout: 255 seconds) |
| 2023-04-19 06:30:21 +0000 | stellacy | (~stellacy@gateway/tor-sasl/stellacy) |
| 2023-04-19 06:43:34 +0000 | mncheck | (~mncheck@193.224.205.254) |
| 2023-04-19 07:16:18 +0000 | <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 07:17:04 +0000 | <geekosaur> | (xmonad needs a --sync option for debugging…) |
| 2023-04-19 07:18:36 +0000 | <geekosaur> | (would also have helped with debugging the windowNavigation issue) |
| 2023-04-19 07:19:46 +0000 | <geekosaur> | aaaaaand it crashed when I restarted qutebrowser in a new session. oy |
| 2023-04-19 07:20:47 +0000 | <geekosaur> | yeh, it's crashing every time now. L29Ah I think you just got lucky |
| 2023-04-19 07:20:58 +0000 | <geekosaur> | and/or there's a timing constraint |
| 2023-04-19 07:27:32 +0000 | <geekosaur> | we don't bind XSynchronize 😞 |
| 2023-04-19 07:27:40 +0000 | <geekosaur> | deal tomorrow |
| 2023-04-19 08:06:38 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2023-04-19 08:07:36 +0000 | <geekosaur> | or realize I can't get back to sleep… |
| 2023-04-19 08:07:38 +0000 | <geekosaur> | welp |
| 2023-04-19 08:07:41 +0000 | <geekosaur> | #10 0x00007fa9d08115fb in XftDrawStringUtf8 () from /lib/x86_64-linux-gnu/libXft.so.2 |
| 2023-04-19 08:10:34 +0000 | <geekosaur> | so it is indeed not in retrieving WM_NAME, it's in trying to render it in the tab |
| 2023-04-19 08:13:42 +0000 | bla | (~bla@79.191.151.29.ipv4.supernova.orange.pl) (Ping timeout: 255 seconds) |
| 2023-04-19 08:23:16 +0000 | mc47 | (~mc47@xmonad/TheMC47) |
| 2023-04-19 08:30:25 +0000 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) (Ping timeout: 250 seconds) |
| 2023-04-19 08:35:22 +0000 | <geekosaur> | gonna hate trying to figure out why the Shrinker isn't; I always get crosseyed looking at those damned things |
| 2023-04-19 09:00:12 +0000 | guazai[m] | (~guazaimat@2001:470:69fc:105::3:3254) (Quit: You have been kicked for being idle) |
| 2023-04-19 09:00:14 +0000 | Solid[m] | (~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle) |
| 2023-04-19 09:00:14 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-04-19 09:00:14 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-04-19 09:17:25 +0000 | hightower3 | (~hightower@213.202.92.246) (Ping timeout: 240 seconds) |
| 2023-04-19 09:21:42 +0000 | <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 09:21:56 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2023-04-19 09:22:04 +0000 | <geekosaur> | (and doesn't handle multiline strings at all afaict) |
| 2023-04-19 09:22:08 +0000 | Solid[m] | (~slot-matr@2001:470:69fc:105::1:a84) |
| 2023-04-19 09:22:22 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-04-19 09:26:00 +0000 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.8) |
| 2023-04-19 09:33:01 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2023-04-19 10:27:27 +0000 | <L29Ah> | sanitizing title before feeding it to a shrinker sounds good to me |
| 2023-04-19 10:27:48 +0000 | <L29Ah> | well, it would be nicer to migrate from String, but it's good enough |
| 2023-04-19 11:47:45 +0000 | td_ | (~td@i5387091D.versanet.de) (Ping timeout: 240 seconds) |
| 2023-04-19 11:47:59 +0000 | td_ | (~td@i5387091D.versanet.de) |
| 2023-04-19 13:12:34 +0000 | hightower2 | (~hightower@95.168.105.23) |
| 2023-04-19 13:37:48 +0000 | hightower2 | (~hightower@95.168.105.23) (Read error: Connection reset by peer) |
| 2023-04-19 14:00:56 +0000 | catman | (~catman@user/catman) |
| 2023-04-19 15:23:01 +0000 | catman | (~catman@user/catman) (Ping timeout: 240 seconds) |
| 2023-04-19 15:28:21 +0000 | <xmonadtrack> | New xmonad-contrib branch created: pull/810 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/810 |
| 2023-04-19 15:30:27 +0000 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.8) |
| 2023-04-19 15:30:33 +0000 | <L29Ah> | :* |
| 2023-04-19 15:36:26 +0000 | <L29Ah> | hmm xmonad hangs for a few secs even with this patch |
| 2023-04-19 15:36:30 +0000 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2023-04-19 15:36:50 +0000 | <L29Ah> | but that's good enough i guess |
| 2023-04-19 15:44:27 +0000 | <geekosaur> | seemed pretty quick here |
| 2023-04-19 15:45:21 +0000 | <L29Ah> | i7-8550U laptop here |
| 2023-04-19 15:45:35 +0000 | <geekosaur> | mine is an older i5 |
| 2023-04-19 15:45:48 +0000 | catman | (~catman@user/catman) |
| 2023-04-19 15:45:50 +0000 | <geekosaur> | and I'm running it in a xephyr in a test harness |
| 2023-04-19 15:47:57 +0000 | <L29Ah> | i guess that might be due to the fact i have several such tabs in my qutebrowser |
| 2023-04-19 15:48:09 +0000 | <L29Ah> | and it blinks them |
| 2023-04-19 15:55:24 +0000 | catman | (~catman@user/catman) (Ping timeout: 255 seconds) |
| 2023-04-19 16:00:08 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2023-04-19 16:00:08 +0000 | Solid[m] | (~slot-matr@2001:470:69fc:105::1:a84) (Quit: You have been kicked for being idle) |
| 2023-04-19 16:00:08 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle) |
| 2023-04-19 16:06:42 +0000 | <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 16:06:54 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2023-04-19 16:07:07 +0000 | Solid[m] | (~slot-matr@2001:470:69fc:105::1:a84) |
| 2023-04-19 16:07:22 +0000 | unclechu | (~unclechu@2001:470:69fc:105::354) |
| 2023-04-19 16:11:07 +0000 | <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 16:11:22 +0000 | <geekosaur> | so another few months and then I have income |
| 2023-04-19 16:11:36 +0000 | <geekosaur> | and can start paying back what I've taken 🙂 |
| 2023-04-19 16:54:38 +0000 | <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 17:19:04 +0000 | jeeeun | (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat) |
| 2023-04-19 17:20:25 +0000 | jeeeun | (~jeeeun@78.40.148.178) |
| 2023-04-19 17:37:01 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2023-04-19 17:59:02 +0000 | jabuxas | (~jabuxas@user/jabuxas) |
| 2023-04-19 17:59:23 +0000 | <jabuxas> | hello |
| 2023-04-19 18:02:56 +0000 | <geekosaur> | hi |
| 2023-04-19 18:03:38 +0000 | <geekosaur> | I saw your messages yesterday but you left before I could reply |
| 2023-04-19 18:04:35 +0000 | <geekosaur> | unfortunately while I think there was an overhaul of ewmhFullscreen recently I can't find it |
| 2023-04-19 18:04:48 +0000 | <geekosaur> | are you running a released version or from git? |
| 2023-04-19 18:05:37 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
| 2023-04-19 18:17:44 +0000 | ft | (~ft@p4fc2a88b.dip0.t-ipconnect.de) |
| 2023-04-19 19:34:53 +0000 | <jabuxas> | git |
| 2023-04-19 19:36:12 +0000 | <jabuxas> | yea i had a blackout yesterday that's why |
| 2023-04-19 19:37:05 +0000 | <jabuxas> | xmonad contrib commit 673de11ca876a4a58cae3a4d52e36260f66aa6cc |
| 2023-04-19 19:39:03 +0000 | <jabuxas> | the problem with ewmh fullscreen specifically was that it was tiling the game client when it shouldnt |
| 2023-04-19 19:39:16 +0000 | <geekosaur> | %gitcontrib 673de11ca87 |
| 2023-04-19 19:39:16 +0000 | <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 19:40:34 +0000 | <geekosaur> | does it behave if you revert that locally? |
| 2023-04-19 19:43:02 +0000 | <geekosaur> | you probably want liskin but I don't know if he's around |
| 2023-04-19 19:52:07 +0000 | <jabuxas> | how would i go about reverting locally? switching commits in stack.yaml and `stack build`? |
| 2023-04-19 19:53:31 +0000 | <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 19:57:33 +0000 | <geekosaur> | oh. so that was just the commit you're on now? |
| 2023-04-19 19:57:42 +0000 | <jabuxas> | yes |
| 2023-04-19 19:58:47 +0000 | <geekosaur> | I'd be interested in knowing if the client still is asserting _NET_WM_STATE_FULLSCREEN on the window |
| 2023-04-19 19:59:46 +0000 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L246 or similar |
| 2023-04-19 20:00:51 +0000 | <geekosaur> | (I have a bunch of debugging / "how do I build a manageHook for this?" keybinds) |
| 2023-04-19 20:02:31 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Ping timeout: 260 seconds) |
| 2023-04-19 20:03:52 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) |
| 2023-04-19 20:08:32 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
| 2023-04-19 20:15:26 +0000 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) |
| 2023-04-19 20:21:19 +0000 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) |
| 2023-04-19 20:33:05 +0000 | <jabuxas> | let me add that and test |
| 2023-04-19 20:33:07 +0000 | <jabuxas> | do you want me to test with or without ewmhFullscreen? |
| 2023-04-19 20:37:02 +0000 | <jabuxas> | https://dpaste.org/yAykK |
| 2023-04-19 20:40:07 +0000 | <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 20:40:18 +0000 | <geekosaur> | so yes, with |
| 2023-04-19 20:40:52 +0000 | <jabuxas> | this is with https://dpaste.org/zOs4g |
| 2023-04-19 20:41:20 +0000 | <geekosaur> | actually according to that paste neither window has _NET_WM_STATE at all |
| 2023-04-19 20:41:45 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 240 seconds) |
| 2023-04-19 20:44:03 +0000 | <geekosaur> | I wonder if it's just sending the message without setting the state, which is an EWMH violation |
| 2023-04-19 20:44:18 +0000 | <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 20:44:54 +0000 | <jabuxas> | https://dpaste.com/CF9ALU8GE#line-368 |
| 2023-04-19 20:48:11 +0000 | <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 20:52:45 +0000 | <jabuxas> | still happens on interact |
| 2023-04-19 20:54:19 +0000 | <geekosaur> | hm. I'm back to thinking this is related to _NET_WM_STATE |
| 2023-04-19 20:55:13 +0000 | <geekosaur> | "on interact" is weird |
| 2023-04-19 20:55:40 +0000 | <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 20:55:54 +0000 | <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 20:56:04 +0000 | <jabuxas> | I can record what's happening if that helps |
| 2023-04-19 20:56:44 +0000 | <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 20:57:06 +0000 | <geekosaur> | the other way it can happen is _NET_WM_STATE changes |
| 2023-04-19 20:57:18 +0000 | <geekosaur> | but you have no _NET_WM_STATE at all |
| 2023-04-19 20:58:08 +0000 | <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 21:01:18 +0000 | <jabuxas> | https://imgur.com/a/MHg4ekp |
| 2023-04-19 21:01:24 +0000 | <geekosaur> | that one is the infamous "bug 4", there are partial workarounds but no fix |
| 2023-04-19 21:01:56 +0000 | <jabuxas> | oh you opened that one |
| 2023-04-19 21:02:50 +0000 | <geekosaur> | not the bug 4 in the current tracker; the one in the old tracker that we couldn't migrate |
| 2023-04-19 21:03:21 +0000 | <geekosaur> | https://code.google.com/archive/p/xmonad/issues/4 |
| 2023-04-19 21:04:33 +0000 | <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 21:05:45 +0000 | <geekosaur> | the StackSet is mathematically lovely but almost pathological UX |
| 2023-04-19 21:08:48 +0000 | <jabuxas> | so fixing it would take a lot of work |
| 2023-04-19 21:13:46 +0000 | hrberg | (~quassel@171.79-160-161.customer.lyse.net) (Ping timeout: 276 seconds) |
| 2023-04-19 21:13:58 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
| 2023-04-19 21:20:11 +0000 | <jabuxas> | if you want to see the bug i uploaded to imgur https://imgur.com/a/mIUmaNU |
| 2023-04-19 21:27:34 +0000 | <geekosaur> | that looks like it's unnmapping and remapping itself |
| 2023-04-19 21:35:07 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2023-04-19 21:35:22 +0000 | <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 21:35:52 +0000 | <geekosaur> | but it's an imperfect solution |
| 2023-04-19 21:44:56 +0000 | catman | (~catman@user/catman) |
| 2023-04-19 21:58:39 +0000 | L29Ah | (~L29Ah@wikipedia/L29Ah) |
| 2023-04-19 22:11:01 +0000 | <jabuxas> | how would i implement that? |
| 2023-04-19 22:17:51 +0000 | <geekosaur> | https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Layout/FocusTracking.hs#L41-L60 |
| 2023-04-19 22:17:52 +0000 | <liskin> | Well that PR of mine lets you disable ewmh fullscreen for individual apps |
| 2023-04-19 22:18:06 +0000 | <liskin> | So that might be a viable workaround |
| 2023-04-19 22:20:12 +0000 | <geekosaur> | I'm looking over your config (that dbus stuff looks familiar 🙂 ) |
| 2023-04-19 22:21:11 +0000 | <geekosaur> | looks like you'd change line 394: wrap what you have in parentheses and put `focusTracking` in front of it |
| 2023-04-19 22:21:39 +0000 | <geekosaur> | after importing XMonad.Layout.FocusTracking |
| 2023-04-19 22:23:41 +0000 | <jabuxas> | doesn't seem to do anything, should i restart X completely? |
| 2023-04-19 22:24:01 +0000 | <jabuxas> | `focusTracking (tiled ||| simpleFloat ||| Mirror tiled ||| Full)` |
| 2023-04-19 22:24:08 +0000 | <geekosaur> | it will only do something with floats |
| 2023-04-19 22:24:33 +0000 | <geekosaur> | it tries to remember and restore where you were when you select the tiled layer |
| 2023-04-19 22:24:57 +0000 | <geekosaur> | to work around that StackSet rotation issue I mentioned earlier |
| 2023-04-19 22:25:03 +0000 | <geekosaur> | ("bug 4") |
| 2023-04-19 22:25:20 +0000 | mncheck | (~mncheck@193.224.205.254) (Ping timeout: 260 seconds) |
| 2023-04-19 22:25:23 +0000 | <jabuxas> | ohhhhhhh i thought we were talking about the other bug |
| 2023-04-19 22:25:25 +0000 | <jabuxas> | my bad |
| 2023-04-19 22:25:37 +0000 | <geekosaur> | nope, I think you need liskin for that |
| 2023-04-19 22:25:57 +0000 | <jabuxas> | yeah now floats aren't changing the max layout, nice :) |
| 2023-04-19 22:26:07 +0000 | <geekosaur> | and I still suspect the _NET_WM_STATE thing is part of the problem |
| 2023-04-19 22:26:45 +0000 | <jabuxas> | interestingly even though it doesn't change on moving or even interacting, it changes when closing the float |
| 2023-04-19 22:29:09 +0000 | <jabuxas> | liskin: are you able to help with that issue? |
| 2023-04-19 22:29:50 +0000 | <geekosaur> | [19 22:17:52] <liskin> Well that PR of mine lets you disable ewmh fullscreen for individual apps |
| 2023-04-19 22:29:50 +0000 | <geekosaur> | [19 22:18:06] <liskin> So that might be a viable workaround |
| 2023-04-19 22:30:17 +0000 | <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-19 22:31:09 +0000 | <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-19 22:31:19 +0000 | <jabuxas> | oh that's what he was talking about, that's why i was confused. ok. |
| 2023-04-19 22:31:39 +0000 | <jabuxas> | i'll try that pr, let me see how i would use that |
| 2023-04-19 22:31:54 +0000 | <geekosaur> | I thought you were already on that commit? |
| 2023-04-19 22:32:02 +0000 | <geekosaur> | (it's already merged) |
| 2023-04-19 22:32:07 +0000 | <jabuxas> | i'm on the commit, i don't know how to use ToggleFullFloat |
| 2023-04-19 22:32:26 +0000 | <geekosaur> | [19 19:39:15] <geekosaur> %gitcontrib 673de11ca87 |
| 2023-04-19 22:32:27 +0000 | <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-19 22:34:28 +0000 | <jabuxas> | doFullFloatSave |
| 2023-04-19 22:34:31 +0000 | <jabuxas> | is that a managehook option? |
| 2023-04-19 22:36:06 +0000 | <geekosaur> | yes |
| 2023-04-19 22:36:29 +0000 | <geekosaur> | it makes a fullscreen window while saving its original state |
| 2023-04-19 22:37:14 +0000 | <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-19 22:38:41 +0000 | <geekosaur> | tbh I'm quite confused by what that video showed |
| 2023-04-19 22:39:30 +0000 | <geekosaur> | but it is possible that all you need is a ManageHook that matches it and fullscreens it |
| 2023-04-19 22:39:51 +0000 | <jabuxas> | why fullscreen it? |
| 2023-04-19 22:39:58 +0000 | <geekosaur> | but I'm worried that will just lead to a map/unmap loop |
| 2023-04-19 22:40:15 +0000 | <geekosaur> | isn't that what you wanted? it's un-fullscreening itself |
| 2023-04-19 22:40:29 +0000 | <geekosaur> | so you would re-fullscreen it |
| 2023-04-19 22:40:49 +0000 | <jabuxas> | the problem is that it tiles itself when it should be floating.. isn't it? |
| 2023-04-19 22:40:52 +0000 | <jabuxas> | at least that's how i'm viewing it |
| 2023-04-19 22:41:31 +0000 | <geekosaur> | that didn't look tiled, it looked floated at +0+0 |
| 2023-04-19 22:41:41 +0000 | <geekosaur> | with a non-fullscreen window |
| 2023-04-19 22:42:33 +0000 | <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-19 22:42:53 +0000 | <geekosaur> | (which is what's weird because that's an X11R3 issue) |
| 2023-04-19 22:43:55 +0000 | <jabuxas> | i'll re-record it brb |
| 2023-04-19 22:46:01 +0000 | <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-19 22:47:25 +0000 | rekahsoft | (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) (Ping timeout: 240 seconds) |
| 2023-04-19 22:47:46 +0000 | <geekosaur> | (applications know nothing about float vs. tiled, that's an internal xmonad thing) |
| 2023-04-19 22:48:19 +0000 | <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-19 22:49:02 +0000 | <geekosaur> | that's what the ManageHook is for |
| 2023-04-19 22:52:16 +0000 | <jabuxas> | but isn't it already set? doCenterFloat |
| 2023-04-19 22:53:28 +0000 | <geekosaur> | doFullFloat? |
| 2023-04-19 22:53:57 +0000 | <geekosaur> | but apparently it's not matching the window that gets remapped because that is not centered |
| 2023-04-19 22:54:21 +0000 | <jabuxas> | https://imgur.com/a/7bWUw1t here is re-recorded, showing that it suddenly tiles itself |
| 2023-04-19 22:54:37 +0000 | <geekosaur> | when it relocates itself to +0+0 / "tiles itself" / whatever, try to get its properties |
| 2023-04-19 22:54:47 +0000 | <jabuxas> | ok |
| 2023-04-19 22:55:53 +0000 | <geekosaur> | yeh, that's tiled |
| 2023-04-19 22:56:07 +0000 | <geekosaur> | a client wouldn't know how to do that itself, it would have to unmap and remap |
| 2023-04-19 22:56:31 +0000 | <geekosaur> | and since there'[s no _NET_WM_STATE the isFullscreen rule doesn't fire |
| 2023-04-19 22:56:51 +0000 | <geekosaur> | so… why doesn't the other one fire? |
| 2023-04-19 22:57:06 +0000 | <geekosaur> | which is why I want to see what props it has after it does that |
| 2023-04-19 22:58:16 +0000 | <jabuxas> | https://dpaste.org/Brocp |
| 2023-04-19 23:00:00 +0000 | <jabuxas> | it didnt change anything did it |
| 2023-04-19 23:11:02 +0000 | <geekosaur> | WM_CLASS is gone so the ManageHook won't match it |
| 2023-04-19 23:11:31 +0000 | <geekosaur> | unless you missed copying it and the second one ends at WM_LOCALE)NAME |
| 2023-04-19 23:11:38 +0000 | <geekosaur> | WM_LOCALE_NAME |
| 2023-04-19 23:11:53 +0000 | <jabuxas> | i'll check again |
| 2023-04-19 23:11:56 +0000 | <jabuxas> | but i think you're right lmao |
| 2023-04-19 23:11:57 +0000 | <jabuxas> | how does it not have a class |
| 2023-04-19 23:12:23 +0000 | <jabuxas> | have you ever seen that before? |
| 2023-04-19 23:13:12 +0000 | <geekosaur> | WM_NORMAL_HINTS is completely different |
| 2023-04-19 23:13:29 +0000 | <geekosaur> | yes, there are broken programs that don't set it |
| 2023-04-19 23:14:27 +0000 | <geekosaur> | notably it sets min and max size the same, so it should be autofloated at its requested size |
| 2023-04-19 23:14:36 +0000 | <jabuxas> | i did an oopsie, it does set class https://dpaste.org/QUiA8 |
| 2023-04-19 23:14:52 +0000 | <geekosaur> | initially it's 1600x900, afterward it's 1912x1047 |
| 2023-04-19 23:15:07 +0000 | <geekosaur> | so it is withdrawing and remapping |
| 2023-04-19 23:16:34 +0000 | <geekosaur> | but why isn't it being matched, then? |
| 2023-04-19 23:17:02 +0000 | <jabuxas> | question of the century |
| 2023-04-19 23:17:51 +0000 | <geekosaur> | hm, or it's resizing and updating WM_NORMAL_HINTS without remapping (a no-no; wms only read it on map) |
| 2023-04-19 23:18:44 +0000 | <geekosaur> | almost tempted to have you dump events, but that produces a _lot_ of crap |
| 2023-04-19 23:19:28 +0000 | <geekosaur> | (X.H.DebugEvents) |
| 2023-04-19 23:21:39 +0000 | <jabuxas> | how is it used? documentation isn't saying |
| 2023-04-19 23:23:57 +0000 | <geekosaur> | oh, right, I didn't document that because it's not really an end user thing, it's a diagnostic tool |
| 2023-04-19 23:24:04 +0000 | <jabuxas> | do I add it like `main = xmonad $ … . debugEventsHook` ? |
| 2023-04-19 23:24:13 +0000 | <geekosaur> | handleEventHook = debugEventsHook |
| 2023-04-19 23:24:32 +0000 | <geekosaur> | (along with manageHook, logHook, layoutHook, etc.) |
| 2023-04-19 23:24:49 +0000 | <jabuxas> | can i <> it? |
| 2023-04-19 23:25:24 +0000 | <geekosaur> | yes |
| 2023-04-19 23:25:39 +0000 | <jabuxas> | where does it go to? the log |
| 2023-04-19 23:25:42 +0000 | <geekosaur> | you can <> everything except the layoutHook |
| 2023-04-19 23:25:45 +0000 | <geekosaur> | yes |
| 2023-04-19 23:25:54 +0000 | <geekosaur> | so you'll need to figure out where the session log is |
| 2023-04-19 23:26:08 +0000 | <geekosaur> | how do you start your session? |
| 2023-04-19 23:26:14 +0000 | <jabuxas> | xinit |
| 2023-04-19 23:26:37 +0000 | <geekosaur> | oh. you'll need to restart it, redirecting xinit's output to a file |
| 2023-04-19 23:26:50 +0000 | <jabuxas> | `exec xmonad | tee ~/.config/xmonad/xmonad.log` |
| 2023-04-19 23:26:54 +0000 | <jabuxas> | that's how i start it |
| 2023-04-19 23:27:19 +0000 | <geekosaur> | exec isn't doing you any good there |
| 2023-04-19 23:27:33 +0000 | <jabuxas> | that's inside .xinitrc |
| 2023-04-19 23:27:36 +0000 | <geekosaur> | in that case though you should see the events in xmonad.log |
| 2023-04-19 23:28:33 +0000 | <jabuxas> | i'll restart either way because it's not writing anything to that file |
| 2023-04-19 23:28:45 +0000 | <jabuxas> | at least not any of the logs you're waiting for |
| 2023-04-19 23:28:56 +0000 | <jabuxas> | just what was there before |
| 2023-04-19 23:30:56 +0000 | <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-19 23:31:34 +0000 | <geekosaur> | and you really don;t want it responding to a lot of stuff, mostly it should stay out of the way |
| 2023-04-19 23:32:08 +0000 | <jabuxas> | it just has normal logs that normally appear there from apps https://bpa.st/AAKAO |
| 2023-04-19 23:32:36 +0000 | <jabuxas> | handleEventHook = -- Hacks.windowedFullscreenFixEventHook swallowEventHook (className =? "Alacritty" <||> className =? "kitty" <||> className =? "XTerm") (return True) <> Hacks.trayerPaddingXmobarEventHook <> debugEventsHook <> myEventHook, |
| 2023-04-19 23:32:58 +0000 | <jabuxas> | the tabs messed it up |
| 2023-04-19 23:33:24 +0000 | <geekosaur> | and lack of newlines. this isn't matrix or discord |
| 2023-04-19 23:34:10 +0000 | <jabuxas> | still figuring out how to properly do things in weechat |
| 2023-04-19 23:35:12 +0000 | <geekosaur> | it's best not to paste code directly into irc at all |
| 2023-04-19 23:35:40 +0000 | <geekosaur> | it'll get mangled, it'll get interrupted by join/part messages, it'll be generally annoying |
| 2023-04-19 23:36:10 +0000 | <jabuxas> | oh yeah, now i got the log |
| 2023-04-19 23:36:24 +0000 | <jabuxas> | needed to `startx > ~/.Xlog 2>&1` |
| 2023-04-19 23:36:32 +0000 | <jabuxas> | i'll start the game now |
| 2023-04-19 23:42:26 +0000 | <jabuxas> | https://0x0.st/H8I1.txt |
| 2023-04-19 23:45:06 +0000 | <geekosaur> | hm, I have some bugs I need to fix 😕 |
| 2023-04-19 23:46:07 +0000 | <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-19 23:46:45 +0000 | <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-19 23:50:43 +0000 | <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-19 23:57:12 +0000 | <geekosaur> | I think I caught it unmapping, remapping, then setting the mandatory properties |
| 2023-04-19 23:57:18 +0000 | <geekosaur> | wrong order |