| 2025-09-21 00:19:39 +0200 | Guest5304 | (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Changing host) |
| 2025-09-21 00:19:39 +0200 | Guest5304 | (~ml|@user/ml/x-5298235) ml| |
| 2025-09-21 00:40:14 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 00:40:21 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Write error: Broken pipe) |
| 2025-09-21 00:44:47 +0200 | Guest5304 | (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.4.2) |
| 2025-09-21 00:45:13 +0200 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2025-09-21 01:01:29 +0200 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.4.2) |
| 2025-09-21 01:01:49 +0200 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2025-09-21 01:02:05 +0200 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2025-09-21 01:02:26 +0200 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2025-09-21 01:24:54 +0200 | Digit | (~user@user/digit) (Remote host closed the connection) |
| 2025-09-21 01:25:51 +0200 | Digitteknohippie | (~user@user/digit) Digit |
| 2025-09-21 02:07:05 +0200 | hiecaq | (~hiecaq@user/hiecaq) hiecaq |
| 2025-09-21 05:46:51 +0200 | ChubaDuba | (~ChubaDuba@79.136.182.14) ChubaDuba |
| 2025-09-21 08:25:57 +0200 | ChubaDuba | (~ChubaDuba@79.136.182.14) (Quit: WeeChat 4.6.3) |
| 2025-09-21 08:52:31 +0200 | Digitteknohippie | Digit |
| 2025-09-21 10:09:13 +0200 | aplainzetakind | (~aplainzet@37.155.33.61) aplainzetakind |
| 2025-09-21 10:09:33 +0200 | redgloboli_ | (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
| 2025-09-21 10:11:16 +0200 | redgloboli | (~redglobol@user/redgloboli) redgloboli |
| 2025-09-21 10:27:46 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 10:34:26 +0200 | <aplainzetakind> | geekosaur: Worked almost perfectly, thanks. One remark: had to do `gsettings set com.linuxmint.desktop mate-window-manager xmonad` instead of what's there, so that changed since the guide was last updated I guess. An insignificant annoyance is that mate-panel appears behind windows. I set it to doFloat in the config, but it only draws on top when killed and restarted, when new windows join the stack it goes behind again (which sounds like it's not a |
| 2025-09-21 10:34:26 +0200 | <aplainzetakind> | ctually floating). Can I do something about that? Another thing is I see many `X11 error: BadAccess (attempt to access private resource denied), request code=28, error code=10` errors in the logs when I start XMonad from the terminal and watch the output, but I don't experience anything misbehaving along with those. I'm not sure if those errors occur when it's started "properly". |
| 2025-09-21 10:58:04 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-21 11:10:16 +0200 | aplainzetakind | (~aplainzet@37.155.33.61) (Remote host closed the connection) |
| 2025-09-21 11:13:17 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 11:15:19 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Client Quit) |
| 2025-09-21 11:15:36 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 11:31:06 +0200 | Miroboru | (~myrvoll@84.214.174.128) (Remote host closed the connection) |
| 2025-09-21 11:43:20 +0200 | Miroboru | (~myrvoll@84.214.174.128) Miroboru |
| 2025-09-21 11:53:05 +0200 | Natch | (~natch@c-92-34-15-120.bbcust.telenor.se) (Server closed connection) |
| 2025-09-21 11:58:23 +0200 | Natch | (~natch@c-92-34-15-120.bbcust.telenor.se) Natch |
| 2025-09-21 12:18:03 +0200 | assface | (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-21 14:04:11 +0200 | assf | (~assf@68.183.200.207) |
| 2025-09-21 14:47:53 +0200 | assf | (~assf@68.183.200.207) (Quit: Client closed) |
| 2025-09-21 16:50:15 +0200 | MrElendig | (~Urist@archlinux/op/MrElendig) (Quit: cat) |
| 2025-09-21 16:52:49 +0200 | <geekosaur> | you should be using ManageDocks instead of trying to manage mate-panel directly |
| 2025-09-21 16:53:18 +0200 | <geekosaur> | whether it's "behind" or "above" won't matter in that case because xmonad won't place windows where the docks are |
| 2025-09-21 16:54:47 +0200 | <geekosaur> | request 28 is XGrabButton. that's somewhat weird, is something else already managing your mouse? |
| 2025-09-21 16:58:01 +0200 | MrElendig | (~Urist@archlinux/op/MrElendig) MrElendig |
| 2025-09-21 17:42:56 +0200 | hiecaq | (~hiecaq@user/hiecaq) (Remote host closed the connection) |
| 2025-09-21 17:59:40 +0200 | Buliarou1 | (~gypsydang@46.232.210.139) Buliarous |
| 2025-09-21 18:02:57 +0200 | Enrico63 | (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) Enrico63 |
| 2025-09-21 18:03:06 +0200 | aplainzetakind | (~aplainzet@37.155.33.61) aplainzetakind |
| 2025-09-21 18:05:33 +0200 | <Enrico63> | Re-asking, as I didn't get any answer yet (I've checked the logs). |
| 2025-09-21 18:05:34 +0200 | <Enrico63> | Layout related question. I've been using ThreeColMid for a week or so, and now I'm trying ThreeCol. But for some reason I'd prefer to have the main column as the right-most column. Is there a solution? The reason is that most windows are textual (browser, terminal, ...), and text starts at the left (yes, for LTR scripts), so having the main column |
| 2025-09-21 18:05:34 +0200 | <Enrico63> | to the left means that the main column text begins as far as possible from the left end of the monitor. ThreeColMid reduces this problem a bit. But ultimately, I think I'd prefer an hypothetical ThreeColRight |
| 2025-09-21 18:07:38 +0200 | <aplainzetakind> | I don't think anything else is managing the mouse. What sort of thing would that be anyway? |
| 2025-09-21 18:08:14 +0200 | <Leary> | Enrico63: Try X.L.Reflect. |
| 2025-09-21 18:15:00 +0200 | <Enrico63> | Leary, wow, thanks! |
| 2025-09-21 18:17:17 +0200 | <aplainzetakind> | And concerning ManageDocks, I already use desktopConfig, which seems to use `docks` anyway. And my windows get away from xmobar when I launch it, so it seems to kind of work, but for some reason mate-panel is not treated the same? |
| 2025-09-21 18:30:59 +0200 | <geekosaur> | it should be, it sets struts as well |
| 2025-09-21 18:33:25 +0200 | <geekosaur> | https://paste.tomsmeding.com/jBYoFaTY note _NET_WM_STRUT_PARTIAL and _NET_WM_STRUT toward the top |
| 2025-09-21 18:33:51 +0200 | <geekosaur> | (I'm not sure why paste.tomsmeding.com doesn't render the AA icons correctly) |
| 2025-09-21 18:43:35 +0200 | <aplainzetakind> | Ah, OK. Here's the thing. I autohide the panel, so it expands when my pointer hits the bottom. Struts apparently aren't aware of that, because it's 1px tall. If I disable autohiding, then windows get away as expected. |
| 2025-09-21 18:43:57 +0200 | <aplainzetakind> | So for my use case, some kind of "always on top" behaviour is really better. |
| 2025-09-21 18:44:42 +0200 | assf | (~assf@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 18:47:09 +0200 | <geekosaur> | you'll have to convince the panel to do that, since EWMH specifies that panels are self-managing and window managers can only react to them. (Our toggle keybinding is technically a violation of EWMH.) It may also mean mate-panel doesn't change its struts when it expands, which I think is also a violation. |
| 2025-09-21 18:48:28 +0200 | <geekosaur> | also our toggle binding won't work right if the panel's on top. (there is a way to do it, it's somewhat annoying though. You'd need a handleEventHook that raised the panel on every run.) |
| 2025-09-21 18:48:49 +0200 | <aplainzetakind> | The moment I click on the panel with xprop, it is expanded, and reads _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 1 |
| 2025-09-21 18:49:02 +0200 | <aplainzetakind> | So it seems it doesn't change really. |
| 2025-09-21 18:49:32 +0200 | <geekosaur> | what might work better would be not using autohide, but instead using toggleStruts with the default being off instead of on: https://github.com/geekosaur/xmonad.hs/blob/hilfy-2023/xmonad.hs#L183 |
| 2025-09-21 18:51:03 +0200 | <aplainzetakind> | Well I have gaps and the panel being partially visible through the gaps makes things pretty ugly. |
| 2025-09-21 18:52:20 +0200 | <geekosaur> | then I think your only option is to file a bug against mate-panel |
| 2025-09-21 18:55:03 +0200 | <geekosaur> | okay, I just reproduced your issue here (Ubuntu, but Mint at least used to be based on Ubuntu). this is clearly a mate-panel bug and about the only possible workaround is the handleEventHook I mentioned |
| 2025-09-21 18:59:19 +0200 | <aplainzetakind> | Alright. Thanks a lot. I will open an issue on the mate-panel repo. I don't really have much use for the panel, I only need it to open the main mint menu (which seems not to be accessible without the panel). And I can have a keyboard shortcut for the menu too, so the panel could remain always hidden for all I care (except unfortunately that's not an option). I'll just live with its accidental expansions. |
| 2025-09-21 19:04:23 +0200 | assf | (~assf@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Ping timeout: 250 seconds) |
| 2025-09-21 19:14:52 +0200 | <haskellbridge> | <geekosaur (@geekosaur:matrix.org)> If you're not using it, you can remove it |
| 2025-09-21 19:19:32 +0200 | <aplainzetakind> | I have no other way to access the menu without it, it seems (or I failed to find how). |
| 2025-09-21 19:23:01 +0200 | <geekosaur> | mm, right, fi the applet isn't running the menu key isn't bound |
| 2025-09-21 19:24:31 +0200 | aplainzetakind | (~aplainzet@37.155.33.61) (Remote host closed the connection) |
| 2025-09-21 19:27:26 +0200 | aplainzetakind | (~aplainzet@37.155.33.61) aplainzetakind |
| 2025-09-21 19:55:48 +0200 | assf | (~assf@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 20:10:15 +0200 | assf | (~assf@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Ping timeout: 250 seconds) |
| 2025-09-21 20:13:36 +0200 | <haskellbridge> | <geekosaur (@geekosaur:matrix.org)> Also you can point to xmobar as to strut handli |
| 2025-09-21 20:13:51 +0200 | <haskellbridge> | <geekosaur (@geekosaur:matrix.org)> * handling |
| 2025-09-21 20:17:05 +0200 | Enrico63 | (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed) |
| 2025-09-21 20:31:26 +0200 | ximon | (~ximon@user/ximon) ximon |
| 2025-09-21 20:39:54 +0200 | ximon | (~ximon@user/ximon) (Quit: Client closed) |
| 2025-09-21 21:29:00 +0200 | Enrico63 | (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) Enrico63 |
| 2025-09-21 22:00:26 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 256 seconds) |
| 2025-09-21 22:00:31 +0200 | ft | (~ft@p4fc2a25a.dip0.t-ipconnect.de) (Ping timeout: 256 seconds) |
| 2025-09-21 22:01:11 +0200 | ft | (~ft@p4fc2a25a.dip0.t-ipconnect.de) ft |
| 2025-09-21 22:19:57 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-09-21 23:17:24 +0200 | apla41942 | (~aplainzet@146.70.198.196) aplainzetakind |
| 2025-09-21 23:17:30 +0200 | apla41942 | (~aplainzet@146.70.198.196) (Remote host closed the connection) |
| 2025-09-21 23:19:42 +0200 | aplainzetakind | (~aplainzet@37.155.33.61) (Ping timeout: 252 seconds) |
| 2025-09-21 23:52:50 +0200 | Enrico63 | (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed) |