Logs: liberachat/#xmonad
| 2025-09-20 19:36:06 | <geekosaur> | it should be possible to modify the StackSet directly and call refresh, but there's nothing to do it right now and you would have to deal with the possibility of it being visible elsewhere yourself |
| 2025-09-20 19:36:47 | <haskellbridge> | <iqubic (she/her)> Yeah... the more I think about it, the less I actually want this. |
| 2025-09-20 19:41:51 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-20 19:42:02 | <geekosaur> | maybe what you really want is IndependentScreens? but it's pretty invasive |
| 2025-09-20 19:43:30 | → | assface joins (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-20 20:09:50 | <haskellbridge> | <iqubic (she/her)> Actually, it turns out that I don't want greedyViewScreen after all Using it for a few minutes is screwing with me. |
| 2025-09-20 20:11:51 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-20 20:29:57 | <haskellbridge> | <iqubic (she/her)> Is it possible to replace "statusBarPropTo" with a similar function that creates a statusBarConfig, but doesn't also set up a PP? Because I have decided that I don't actually want a prop reader on my secondary xmobar. https://github.com/IQubic/nixos-config/blob/master/hm/xmonad/XMonad.hs#L219 |
| 2025-09-20 20:31:20 | <haskellbridge> | <iqubic (she/her)> I have no stdInReaders or PropReaders or anything there. |
| 2025-09-20 20:38:49 | <liskin> | I vaguely remember that my config probably does something like that... |
| 2025-09-20 20:39:21 | <liskin> | I mean I do have propreaders in all, but only one of them is produced by a PP |
| 2025-09-20 20:40:07 | <liskin> | The others come from a custom logHook, yet all the xmobars are managed by dynamicSBs or whatever it's called |
| 2025-09-20 20:42:18 | <geekosaur> | you can just log to a property that nothing's paying any attention to |
| 2025-09-20 20:42:25 | <liskin> | Hm, https://github.com/liskin/dotfiles/blob/home/.xmonad/xmonad.hs#L358, not the most obvious way to do it I guess |
| 2025-09-20 20:43:14 | → | assface joins (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-20 20:44:17 | <geekosaur> | a property is just some data associated with a particular window (the root window, in this case). they don't inherently have meaning |
| 2025-09-20 20:44:58 | <liskin> | Yeah good point |
| 2025-09-20 20:54:56 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-20 21:01:57 | × | ml| quits (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.4.2) |
| 2025-09-20 21:02:18 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:02:37 | ml| | is now known as Guest9918 |
| 2025-09-20 21:02:39 | × | Guest9918 quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Client Quit) |
| 2025-09-20 21:03:11 | → | ml|_ joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:03:52 | × | ml|_ quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Client Quit) |
| 2025-09-20 21:04:18 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:04:22 | × | ml| quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Client Quit) |
| 2025-09-20 21:11:48 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:12:07 | ml| | is now known as Guest7555 |
| 2025-09-20 21:19:52 | × | Guest7555 quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Quit: WeeChat 4.4.2) |
| 2025-09-20 21:27:14 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:27:33 | ml| | is now known as Guest9864 |
| 2025-09-20 21:29:30 | × | Guest9864 quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Client Quit) |
| 2025-09-20 21:29:51 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:30:10 | ml| | is now known as Guest9943 |
| 2025-09-20 21:30:26 | × | Guest9943 quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Client Quit) |
| 2025-09-20 21:35:47 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:36:06 | ml| | is now known as Guest5174 |
| 2025-09-20 21:40:34 | × | Guest5174 quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Client Quit) |
| 2025-09-20 21:41:01 | → | ml| joins (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) |
| 2025-09-20 21:41:19 | ml| | is now known as Guest5304 |
| 2025-09-20 22:19:39 | × | Guest5304 quits (~ml|@c-174-48-137-231.hsd1.fl.comcast.net) (Changing host) |
| 2025-09-20 22:19:39 | → | Guest5304 joins (~ml|@user/ml/x-5298235) |
| 2025-09-20 22:40:14 | → | assface joins (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-20 22:40:21 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Write error: Broken pipe) |
| 2025-09-20 22:44:47 | × | Guest5304 quits (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.4.2) |
| 2025-09-20 22:45:13 | → | ml| joins (~ml|@user/ml/x-5298235) |
| 2025-09-20 23:01:29 | × | ml| quits (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.4.2) |
| 2025-09-20 23:01:49 | → | ml| joins (~ml|@user/ml/x-5298235) |
| 2025-09-20 23:02:05 | × | ml| quits (~ml|@user/ml/x-5298235) (Client Quit) |
| 2025-09-20 23:02:26 | → | ml| joins (~ml|@user/ml/x-5298235) |
| 2025-09-20 23:24:54 | × | Digit quits (~user@user/digit) (Remote host closed the connection) |
| 2025-09-20 23:25:51 | → | Digitteknohippie joins (~user@user/digit) |
| 2025-09-21 00:07:05 | → | hiecaq joins (~hiecaq@user/hiecaq) |
| 2025-09-21 03:46:51 | → | ChubaDuba joins (~ChubaDuba@79.136.182.14) |
| 2025-09-21 06:25:57 | × | ChubaDuba quits (~ChubaDuba@79.136.182.14) (Quit: WeeChat 4.6.3) |
| 2025-09-21 06:52:31 | Digitteknohippie | is now known as Digit |
| 2025-09-21 08:09:13 | → | aplainzetakind joins (~aplainzet@37.155.33.61) |
| 2025-09-21 08:09:33 | × | redgloboli_ quits (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
| 2025-09-21 08:11:16 | → | redgloboli joins (~redglobol@user/redgloboli) |
| 2025-09-21 08:27:46 | → | assface joins (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 08:34:26 | <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 08:34:26 | <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 08:58:04 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-21 09:10:16 | × | aplainzetakind quits (~aplainzet@37.155.33.61) (Remote host closed the connection) |
| 2025-09-21 09:13:17 | → | assface joins (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 09:15:19 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Client Quit) |
| 2025-09-21 09:15:36 | → | assface joins (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 09:31:06 | × | Miroboru quits (~myrvoll@84.214.174.128) (Remote host closed the connection) |
| 2025-09-21 09:43:20 | → | Miroboru joins (~myrvoll@84.214.174.128) |
| 2025-09-21 09:53:05 | × | Natch quits (~natch@c-92-34-15-120.bbcust.telenor.se) (Server closed connection) |
| 2025-09-21 09:58:23 | → | Natch joins (~natch@c-92-34-15-120.bbcust.telenor.se) |
| 2025-09-21 10:18:03 | × | assface quits (~assface@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-21 12:04:11 | → | assf joins (~assf@68.183.200.207) |
| 2025-09-21 12:47:53 | × | assf quits (~assf@68.183.200.207) (Quit: Client closed) |
| 2025-09-21 14:50:15 | × | MrElendig quits (~Urist@archlinux/op/MrElendig) (Quit: cat) |
| 2025-09-21 14:52:49 | <geekosaur> | you should be using ManageDocks instead of trying to manage mate-panel directly |
| 2025-09-21 14:53:18 | <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 14:54:47 | <geekosaur> | request 28 is XGrabButton. that's somewhat weird, is something else already managing your mouse? |
| 2025-09-21 14:58:01 | → | MrElendig joins (~Urist@archlinux/op/MrElendig) |
| 2025-09-21 15:42:56 | × | hiecaq quits (~hiecaq@user/hiecaq) (Remote host closed the connection) |
| 2025-09-21 15:59:40 | → | Buliarou1 joins (~gypsydang@46.232.210.139) |
| 2025-09-21 16:02:57 | → | Enrico63 joins (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) |
| 2025-09-21 16:03:06 | → | aplainzetakind joins (~aplainzet@37.155.33.61) |
| 2025-09-21 16:05:33 | <Enrico63> | Re-asking, as I didn't get any answer yet (I've checked the logs). |
| 2025-09-21 16:05:34 | <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 16:05:34 | <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 16:07:38 | <aplainzetakind> | I don't think anything else is managing the mouse. What sort of thing would that be anyway? |
| 2025-09-21 16:08:14 | <Leary> | Enrico63: Try X.L.Reflect. |
| 2025-09-21 16:15:00 | <Enrico63> | Leary, wow, thanks! |
| 2025-09-21 16:17:17 | <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 16:30:59 | <geekosaur> | it should be, it sets struts as well |
| 2025-09-21 16:33:25 | <geekosaur> | https://paste.tomsmeding.com/jBYoFaTY note _NET_WM_STRUT_PARTIAL and _NET_WM_STRUT toward the top |
| 2025-09-21 16:33:51 | <geekosaur> | (I'm not sure why paste.tomsmeding.com doesn't render the AA icons correctly) |
| 2025-09-21 16:43:35 | <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 16:43:57 | <aplainzetakind> | So for my use case, some kind of "always on top" behaviour is really better. |
| 2025-09-21 16:44:42 | → | assf joins (~assf@dslb-002-201-020-218.002.201.pools.vodafone-ip.de) |
| 2025-09-21 16:47:09 | <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 16:48:28 | <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 16:48:49 | <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 16:49:02 | <aplainzetakind> | So it seems it doesn't change really. |
All times are in UTC.