Logs: liberachat/#xmonad
| 2023-04-19 22:31:54 | <geekosaur> | I thought you were already on that commit? |
| 2023-04-19 22:32:02 | <geekosaur> | (it's already merged) |
| 2023-04-19 22:32:07 | <jabuxas> | i'm on the commit, i don't know how to use ToggleFullFloat |
| 2023-04-19 22:32:26 | <geekosaur> | [19 19:39:15] <geekosaur> %gitcontrib 673de11ca87 |
| 2023-04-19 22:32:27 | <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 | <jabuxas> | doFullFloatSave |
| 2023-04-19 22:34:31 | <jabuxas> | is that a managehook option? |
| 2023-04-19 22:36:06 | <geekosaur> | yes |
| 2023-04-19 22:36:29 | <geekosaur> | it makes a fullscreen window while saving its original state |
| 2023-04-19 22:37:14 | <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 | <geekosaur> | tbh I'm quite confused by what that video showed |
| 2023-04-19 22:39:30 | <geekosaur> | but it is possible that all you need is a ManageHook that matches it and fullscreens it |
| 2023-04-19 22:39:51 | <jabuxas> | why fullscreen it? |
| 2023-04-19 22:39:58 | <geekosaur> | but I'm worried that will just lead to a map/unmap loop |
| 2023-04-19 22:40:15 | <geekosaur> | isn't that what you wanted? it's un-fullscreening itself |
| 2023-04-19 22:40:29 | <geekosaur> | so you would re-fullscreen it |
| 2023-04-19 22:40:49 | <jabuxas> | the problem is that it tiles itself when it should be floating.. isn't it? |
| 2023-04-19 22:40:52 | <jabuxas> | at least that's how i'm viewing it |
| 2023-04-19 22:41:31 | <geekosaur> | that didn't look tiled, it looked floated at +0+0 |
| 2023-04-19 22:41:41 | <geekosaur> | with a non-fullscreen window |
| 2023-04-19 22:42:33 | <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 | <geekosaur> | (which is what's weird because that's an X11R3 issue) |
| 2023-04-19 22:43:55 | <jabuxas> | i'll re-record it brb |
| 2023-04-19 22:46:01 | <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 | × | rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-04-174-88-193-177.dsl.bell.ca) (Ping timeout: 240 seconds) |
| 2023-04-19 22:47:46 | <geekosaur> | (applications know nothing about float vs. tiled, that's an internal xmonad thing) |
| 2023-04-19 22:48:19 | <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 | <geekosaur> | that's what the ManageHook is for |
| 2023-04-19 22:52:16 | <jabuxas> | but isn't it already set? doCenterFloat |
| 2023-04-19 22:53:28 | <geekosaur> | doFullFloat? |
| 2023-04-19 22:53:57 | <geekosaur> | but apparently it's not matching the window that gets remapped because that is not centered |
| 2023-04-19 22:54:21 | <jabuxas> | https://imgur.com/a/7bWUw1t here is re-recorded, showing that it suddenly tiles itself |
| 2023-04-19 22:54:37 | <geekosaur> | when it relocates itself to +0+0 / "tiles itself" / whatever, try to get its properties |
| 2023-04-19 22:54:47 | <jabuxas> | ok |
| 2023-04-19 22:55:53 | <geekosaur> | yeh, that's tiled |
| 2023-04-19 22:56:07 | <geekosaur> | a client wouldn't know how to do that itself, it would have to unmap and remap |
| 2023-04-19 22:56:31 | <geekosaur> | and since there'[s no _NET_WM_STATE the isFullscreen rule doesn't fire |
| 2023-04-19 22:56:51 | <geekosaur> | so… why doesn't the other one fire? |
| 2023-04-19 22:57:06 | <geekosaur> | which is why I want to see what props it has after it does that |
| 2023-04-19 22:58:16 | <jabuxas> | https://dpaste.org/Brocp |
| 2023-04-19 23:00:00 | <jabuxas> | it didnt change anything did it |
| 2023-04-19 23:11:02 | <geekosaur> | WM_CLASS is gone so the ManageHook won't match it |
| 2023-04-19 23:11:31 | <geekosaur> | unless you missed copying it and the second one ends at WM_LOCALE)NAME |
| 2023-04-19 23:11:38 | <geekosaur> | WM_LOCALE_NAME |
| 2023-04-19 23:11:53 | <jabuxas> | i'll check again |
| 2023-04-19 23:11:56 | <jabuxas> | but i think you're right lmao |
| 2023-04-19 23:11:57 | <jabuxas> | how does it not have a class |
| 2023-04-19 23:12:23 | <jabuxas> | have you ever seen that before? |
| 2023-04-19 23:13:12 | <geekosaur> | WM_NORMAL_HINTS is completely different |
| 2023-04-19 23:13:29 | <geekosaur> | yes, there are broken programs that don't set it |
| 2023-04-19 23:14:27 | <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 | <jabuxas> | i did an oopsie, it does set class https://dpaste.org/QUiA8 |
| 2023-04-19 23:14:52 | <geekosaur> | initially it's 1600x900, afterward it's 1912x1047 |
| 2023-04-19 23:15:07 | <geekosaur> | so it is withdrawing and remapping |
| 2023-04-19 23:16:34 | <geekosaur> | but why isn't it being matched, then? |
| 2023-04-19 23:17:02 | <jabuxas> | question of the century |
| 2023-04-19 23:17:51 | <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 | <geekosaur> | almost tempted to have you dump events, but that produces a _lot_ of crap |
| 2023-04-19 23:19:28 | <geekosaur> | (X.H.DebugEvents) |
| 2023-04-19 23:21:39 | <jabuxas> | how is it used? documentation isn't saying |
| 2023-04-19 23:23:57 | <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 | <jabuxas> | do I add it like `main = xmonad $ … . debugEventsHook` ? |
| 2023-04-19 23:24:13 | <geekosaur> | handleEventHook = debugEventsHook |
| 2023-04-19 23:24:32 | <geekosaur> | (along with manageHook, logHook, layoutHook, etc.) |
| 2023-04-19 23:24:49 | <jabuxas> | can i <> it? |
| 2023-04-19 23:25:24 | <geekosaur> | yes |
| 2023-04-19 23:25:39 | <jabuxas> | where does it go to? the log |
| 2023-04-19 23:25:42 | <geekosaur> | you can <> everything except the layoutHook |
| 2023-04-19 23:25:45 | <geekosaur> | yes |
| 2023-04-19 23:25:54 | <geekosaur> | so you'll need to figure out where the session log is |
| 2023-04-19 23:26:08 | <geekosaur> | how do you start your session? |
| 2023-04-19 23:26:14 | <jabuxas> | xinit |
| 2023-04-19 23:26:37 | <geekosaur> | oh. you'll need to restart it, redirecting xinit's output to a file |
| 2023-04-19 23:26:50 | <jabuxas> | `exec xmonad | tee ~/.config/xmonad/xmonad.log` |
| 2023-04-19 23:26:54 | <jabuxas> | that's how i start it |
| 2023-04-19 23:27:19 | <geekosaur> | exec isn't doing you any good there |
| 2023-04-19 23:27:33 | <jabuxas> | that's inside .xinitrc |
| 2023-04-19 23:27:36 | <geekosaur> | in that case though you should see the events in xmonad.log |
| 2023-04-19 23:28:33 | <jabuxas> | i'll restart either way because it's not writing anything to that file |
| 2023-04-19 23:28:45 | <jabuxas> | at least not any of the logs you're waiting for |
| 2023-04-19 23:28:56 | <jabuxas> | just what was there before |
| 2023-04-19 23:30:56 | <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 | <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 | <jabuxas> | it just has normal logs that normally appear there from apps https://bpa.st/AAKAO |
| 2023-04-19 23:32:36 | <jabuxas> | handleEventHook = -- Hacks.windowedFullscreenFixEventHook swallowEventHook (className =? "Alacritty" <||> className =? "kitty" <||> className =? "XTerm") (return True) <> Hacks.trayerPaddingXmobarEventHook <> debugEventsHook <> myEventHook, |
| 2023-04-19 23:32:58 | <jabuxas> | the tabs messed it up |
| 2023-04-19 23:33:24 | <geekosaur> | and lack of newlines. this isn't matrix or discord |
| 2023-04-19 23:34:10 | <jabuxas> | still figuring out how to properly do things in weechat |
| 2023-04-19 23:35:12 | <geekosaur> | it's best not to paste code directly into irc at all |
| 2023-04-19 23:35:40 | <geekosaur> | it'll get mangled, it'll get interrupted by join/part messages, it'll be generally annoying |
| 2023-04-19 23:36:10 | <jabuxas> | oh yeah, now i got the log |
| 2023-04-19 23:36:24 | <jabuxas> | needed to `startx > ~/.Xlog 2>&1` |
| 2023-04-19 23:36:32 | <jabuxas> | i'll start the game now |
| 2023-04-19 23:42:26 | <jabuxas> | https://0x0.st/H8I1.txt |
| 2023-04-19 23:45:06 | <geekosaur> | hm, I have some bugs I need to fix 😕 |
| 2023-04-19 23:46:07 | <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 | <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 | <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 | <geekosaur> | I think I caught it unmapping, remapping, then setting the mandatory properties |
| 2023-04-19 23:57:18 | <geekosaur> | wrong order |
All times are in UTC.