Logs: liberachat/#xmonad
| 2025-09-09 13:37:07 | × | hightower4 quits (~hightower@cpe-94-253-190-65.zg.cable.xnet.hr) (Ping timeout: 255 seconds) |
| 2025-09-09 15:58:39 | → | ft joins (~ft@p4fc2a25a.dip0.t-ipconnect.de) |
| 2025-09-09 16:34:02 | × | mkoskar quits (~mkoskar@user/mkoskar) (Quit: mkoskar) |
| 2025-09-09 16:35:09 | → | mkoskar joins (~mkoskar@user/mkoskar) |
| 2025-09-09 16:53:02 | × | yaslam quits (~yaslam@user/yaslam) (Ping timeout: 256 seconds) |
| 2025-09-09 16:53:53 | → | yaslam joins (~yaslam@user/yaslam) |
| 2025-09-09 18:55:38 | <geekosaur> | in light of https://opencollective.com/opensource/updates/public-service-announcement-re-salt-typhoon, can we prune release people on Hackage? |
| 2025-09-09 18:56:56 | <geekosaur> | on the one hand, one might not expect us to be very involved in supply chain attacks… OTOH a window manager is a lovely place to insert code that can do pretty much anything on a system |
| 2025-09-09 18:57:27 | <geekosaur> | (Wayland has some mitigations, but I expect is almost as bad in practice) |
| 2025-09-09 19:29:09 | <L29Ah> | what kind of mitigations does wayland have? |
| 2025-09-09 19:29:26 | <L29Ah> | i expect a wayland compositor having more permissions than X window manager |
| 2025-09-09 19:29:53 | <L29Ah> | as it needs things like direct I/O access unlike the window manager |
| 2025-09-09 19:30:30 | <geekosaur> | right, it's in effect the "X server" |
| 2025-09-09 19:31:04 | <geekosaur> | and the window manager is a plugin to it, and has access to more things than clients do as a result… but can be simpler also, making it easier to audit |
| 2025-09-09 19:32:12 | <geekosaur> | and a lot of stuff that's exposed for client<->window manager and client<->X server intended for window management isn't exposed in a way that lets any other client eavesdrop or potentially inject messages, like it is in X |
| 2025-09-09 19:33:03 | <geekosaur> | ("potentially inject" itself being mitigated by the "send_message" flag, as long as you don't have XTEST or certain other extensions enabled that by default are disabled for very good reason) |
| 2025-09-09 19:37:21 | <geekosaur> | there are ways to restrict those messages, but it's complicated and really easy to get wrong in both directions (that is, restricting either too little or too much) |
| 2025-09-09 19:44:35 | → | ximn joins (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) |
| 2025-09-09 19:44:55 | <ximn> | Hi is there xmonad on Wayland ? Also is xmonad similar to qtile? |
| 2025-09-09 19:45:43 | <ximn> | I have Debian and would like to try it if it is like qtile any suggestions |
| 2025-09-09 19:48:27 | <geekosaur> | not yet, there was some work going on but it seems to have stalled (you can find it on Discourse) |
| 2025-09-09 19:50:40 | <ximn> | Is xmonad good for gaming? |
| 2025-09-09 19:53:45 | <ximn> | How many months is xmonad on Debian forky behind ? |
| 2025-09-09 19:58:30 | <ximn> | What's the display manager that can open xmonad ? |
| 2025-09-09 19:58:33 | <ximn> | Light dm? |
| 2025-09-09 20:07:22 | × | ximn quits (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-09 20:20:59 | → | ximn joins (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) |
| 2025-09-09 20:25:58 | × | tremon quits (~tremon@83.80.159.219) (Quit: getting boxed in) |
| 2025-09-09 20:31:12 | × | ximn quits (~ximn@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-09 20:41:01 | <L29Ah> | i wonder how many of X security critics acutally run their desktops under a MAC |
| 2025-09-09 20:57:41 | <geekosaur> | if you use an OS package then any XDG-compliant display manager should work |
| 2025-09-09 20:58:37 | <geekosaur> | if you install it yourself, there's an example desktop file on the wiki or you can do it the old fashioned way with a "default X session" and .xsession file |
| 2025-09-09 20:59:01 | <L29Ah> | he left |
| 2025-09-09 20:59:23 | <geekosaur> | sigh |
| 2025-09-09 21:55:54 | → | Guest65 joins (~Guest65@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) |
| 2025-09-09 21:55:59 | <Guest65> | is there a prefinished xmonad desktop |
| 2025-09-09 21:56:00 | <Guest65> | ? |
| 2025-09-09 22:01:35 | <geekosaur> | not really, the whole idea is that xmonad is a window manager construction toolkit. |
| 2025-09-09 22:01:46 | <geekosaur> | bluetile exists but it's based on a fairly old version |
| 2025-09-09 22:12:27 | × | Guest65 quits (~Guest65@dslb-002-206-034-018.002.206.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-09-09 23:36:01 | × | ft quits (~ft@p4fc2a25a.dip0.t-ipconnect.de) (Quit: Lost terminal) |
| 2025-09-09 23:51:51 | → | ft joins (~ft@p4fc2a25a.dip0.t-ipconnect.de) |
| 2025-09-09 23:53:58 | × | tv quits (~tv@user/tv) (Quit: derp) |
| 2025-09-09 23:55:05 | → | tv joins (~tv@user/tv) |
| 2025-09-10 01:25:25 | → | sajenim joins (~sajenim@user/sajenim) |
| 2025-09-10 05:23:48 | × | ml| quits (~ml|@user/ml/x-5298235) (Ping timeout: 252 seconds) |
| 2025-09-10 05:26:37 | → | ChubaDuba joins (~ChubaDuba@79.136.183.200) |
| 2025-09-10 05:42:50 | → | ml| joins (~ml|@user/ml/x-5298235) |
| 2025-09-10 06:22:52 | <haskellbridge> | <Solid> geekosaur: I guess we can prune a few of the people who haven't been around for years if you want, but I don't see either of those names as being a big risk |
| 2025-09-10 06:28:52 | <deebo> | xmonad + haskell is in itself true security through obscurity :) |
| 2025-09-10 06:29:00 | → | Solid joins (~slot@xmonad/slotThe) |
| 2025-09-10 06:31:29 | × | ChubaDuba quits (~ChubaDuba@79.136.183.200) (Quit: WeeChat 4.6.3) |
| 2025-09-10 06:35:37 | → | ChubaDuba joins (~ChubaDuba@79.136.183.200) |
| 2025-09-10 06:50:50 | × | Solid quits (~slot@xmonad/slotThe) (Remote host closed the connection) |
| 2025-09-10 07:01:02 | × | ChubaDuba quits (~ChubaDuba@79.136.183.200) (Quit: WeeChat 4.6.3) |
| 2025-09-10 07:35:36 | × | de-vri-es quits (~de-vri-es@voyager.de-vri.es) (Quit: Bathrobe!) |
| 2025-09-10 07:36:02 | → | de-vri-es joins (~de-vri-es@voyager.de-vri.es) |
| 2025-09-10 07:52:34 | × | ft quits (~ft@p4fc2a25a.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-09-10 08:01:35 | × | joshproehl quits (~quassel@user/joshproehl) (Quit: Disappearing act!) |
| 2025-09-10 08:02:47 | → | joshproehl joins (~quassel@user/joshproehl) |
| 2025-09-10 09:19:03 | → | Enrico63 joins (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) |
| 2025-09-10 09:24:51 | <Enrico63> | Hi all, is there anybody available for "reviewing" an xmonad.hs file? Nothing thorough, I'd just like to know if my setup is resonably ok or it has some very ancient deprecated stuff. |
| 2025-09-10 09:24:51 | <Enrico63> | Background: I've been happily using xmonad+xmobar for the last few years, but only in last few days I've hit https://github.com/xmonad/xmonad/issues/245 and successfully adopted the suggested solution of using `refocusLastLayoutHook` and `focusTracking`. I see, however, also the usage of `avoidStruts`, which I don't know what it is.. apparently is |
| 2025-09-10 09:24:52 | <Enrico63> | for avoiding xmonad windows overlapping with other entitites such as xmobar, but I'm not using `avoidStruts` and yet my (non-floating) windows are not overlapping with xmobar. So I wandered more generally about my whole setup. |
| 2025-09-10 09:26:13 | <Enrico63> | Oh, my xmobar.hs is here: https://gist.github.com/Aster89/34747b2ef46bb5e21cc634a87c1d2db1 |
| 2025-09-10 09:42:33 | <haskellbridge> | <Solid> Enrico63: The "withEasySB" function that you use automatically adds "avoidStruts", so you don't have to worry about it |
| 2025-09-10 09:43:14 | <haskellbridge> | <Solid> In general it looks like you went through (at least parts of) the tutorial, which is generally up-to-date and not super deprecated, in the way a few old config might be |
| 2025-09-10 09:43:26 | <haskellbridge> | <Solid> So I wouldn't worry :) |
| 2025-09-10 09:51:51 | <Enrico63> | Thanks! |
| 2025-09-10 10:41:07 | <Enrico63> | I have another question: I've just tried the magnifiers, and I have the feeling that something is off as regards the reloading of xmonad. |
| 2025-09-10 10:41:07 | <Enrico63> | Say I this layout: |
| 2025-09-10 10:41:08 | <Enrico63> | ``` |
| 2025-09-10 10:41:08 | <Enrico63> | threeCol = magnifiercz 1.1 $ ThreeColMid nmaster delta ratio |
| 2025-09-10 10:41:09 | <Enrico63> | ``` |
| 2025-09-10 10:41:09 | <Enrico63> | It works. Now I change it to 1.3, and restart xmonad in place. It takes its time to compile but then I don't see the change in the factor. |
| 2025-09-10 10:41:10 | <Enrico63> | So I revert moentarily to |
| 2025-09-10 10:41:10 | <Enrico63> | ``` |
| 2025-09-10 10:41:11 | <Enrico63> | threeCol = ThreeColMid nmaster delta ratio |
| 2025-09-10 10:41:11 | <Enrico63> | ``` |
| 2025-09-10 10:41:12 | <Enrico63> | rebuild in place, and then change it |
| 2025-09-10 10:41:12 | <Enrico63> | ``` |
| 2025-09-10 10:41:13 | <Enrico63> | threeCol = magnifiercz 1.3 $ ThreeColMid nmaster delta ratio |
| 2025-09-10 10:41:13 | <Enrico63> | ``` |
| 2025-09-10 10:41:14 | <Enrico63> | and rebuild in place. Now I do see the change in the magnifying factor. |
| 2025-09-10 10:41:14 | <Enrico63> | It looks like changing the magnifier and recompiling is not enough for xmonad to digetst the change, and I always have to pass by a non-magnified layout compilation to be able to actually change the layout. |
| 2025-09-10 10:41:15 | <Enrico63> | Is this some known issue? |
| 2025-09-10 10:45:00 | <Leary> | Enrico63: Yes. xmonad can't distinguish static from dynamic configuration changes, so it errs on the side of preserving dynamic config. There's a default binding to load new/default layout config on the current workspace: Mod+Shift+Space |
| 2025-09-10 10:56:21 | <Enrico63> | Where in the world do I find the default configuration of xmonad? I see the datatype at https://hackage.haskell.org/package/xmonad-0.18.0/docs/src/XMonad.Core.html#XConfig but where do I find the values of the defaults? |
| 2025-09-10 10:57:28 | <Enrico63> | I have M+S+space bound to another action, so I'd like add a custom key binding, but I don't know what to bind it to |
| 2025-09-10 10:58:32 | <Leary> | Enrico63: https://hackage.haskell.org/package/xmonad-0.18.0/docs/src/XMonad.Config.html#keys |
| 2025-09-10 11:39:17 | <Enrico63> | Wow, I've spent the last half an hour trying to get this mapping working, and the reason why it wouldn't I think it's unrelatred to xmonad, but maybe you can help. |
| 2025-09-10 11:39:17 | <Enrico63> | My config looked like this: |
| 2025-09-10 11:39:18 | <Enrico63> | ``` |
| 2025-09-10 11:39:18 | <Enrico63> | myConfig = def |
| 2025-09-10 11:39:19 | <Enrico63> | { terminal = "urxvt" |
| 2025-09-10 11:39:19 | <Enrico63> | , modMask = mod4Mask |
| 2025-09-10 11:39:20 | <Enrico63> | } |
| 2025-09-10 11:39:20 | <Enrico63> | `additionalKeysP` myKeys |
| 2025-09-10 11:39:21 | <Enrico63> | myKeys = ("M-<Space>", sendMessage NextLayout) |
| 2025-09-10 11:39:21 | <Enrico63> | : ("M-S-<Space>", spawn "rofi -show combi -theme sidebar.rasi") |
All times are in UTC.