Logs on 2025-05-27 (liberachat/#xmonad)
| 02:07:15 | × | td_ quits (~td@83.135.9.23) (Ping timeout: 265 seconds) |
| 02:08:57 | → | td_ joins (~td@i53870903.versanet.de) |
| 02:13:04 | → | werneta joins (~werneta@syn-071-083-160-242.res.spectrum.com) |
| 03:41:55 | × | dpn quits (~dpn@203.220.95.204) (Ping timeout: 260 seconds) |
| 05:07:04 | → | ChubaDuba joins (~ChubaDuba@46.147.219.70) |
| 06:38:51 | × | werneta quits (~werneta@syn-071-083-160-242.res.spectrum.com) (Ping timeout: 252 seconds) |
| 06:56:24 | × | ChubaDuba quits (~ChubaDuba@46.147.219.70) (Quit: WeeChat 4.6.3) |
| 07:39:27 | → | mc47 joins (~yecinem@host-212-114-138-22.customer.m-online.net) |
| 08:24:16 | × | ft quits (~ft@p3e9bc106.dip0.t-ipconnect.de) (Quit: leaving) |
| 08:51:05 | → | Digitteknohippie joins (~user@user/digit) |
| 08:51:48 | × | Digit quits (~user@user/digit) (Ping timeout: 265 seconds) |
| 09:02:31 | Digitteknohippie | is now known as Digit |
| 09:46:57 | × | mkoskar quits (~mkoskar@user/mkoskar) (Ping timeout: 252 seconds) |
| 09:52:01 | → | mkoskar joins (~mkoskar@user/mkoskar) |
| 12:10:06 | <haskellbridge> | <Plume> Hello, |
| 12:10:06 | <haskellbridge> | ... long message truncated: https://kf8nh.com/_heisenbridge/media/kf8nh.com/aqAYsJlOGhxtEbktQfHYBxjo/nSmy8gQ6tuI (5 lines) |
| 13:26:25 | × | mkoskar quits (~mkoskar@user/mkoskar) (Quit: mkoskar) |
| 13:26:41 | → | mkoskar joins (~mkoskar@user/mkoskar) |
| 13:45:17 | → | Digitteknohippie joins (~user@user/digit) |
| 13:45:40 | × | Digit quits (~user@user/digit) (Ping timeout: 252 seconds) |
| 13:57:06 | Digitteknohippie | is now known as Digit |
| 14:50:10 | <geekosaur> | that sounds somewhat odd, since it's working here |
| 14:52:19 | <geekosaur> | I'm not doing anything special in xmonad, just used MATE's configuration utility to set a cursor scheme |
| 16:08:08 | <haskellbridge> | <Plume> I think I might have an idea why, must be due to me configuring with nix incorrectly, I'll try to fix it! |
| 16:21:52 | × | mc47 quits (~yecinem@host-212-114-138-22.customer.m-online.net) (Ping timeout: 252 seconds) |
| 17:18:39 | → | ft joins (~ft@p3e9bc106.dip0.t-ipconnect.de) |
| 17:21:43 | <haskellbridge> | <Plume> I actually just found this issue that describes perfectly what I'm seeing https://github.com/xmonad/xmonad/pull/352 |
| 17:21:45 | <haskellbridge> | I see that it's merged, but the function mouseDragCursor is nowhere to be found. Is it removed again? |
| 17:22:53 | <haskellbridge> | <Plume> (Correction, it's used internally but not exported, it seems like) |
| 17:27:54 | <geekosaur> | as described in the PR ("introduce a new (non-exported) `mouseDragCursor`") |
| 17:30:00 | <haskellbridge> | <Plume> Yeah sorry, must have missed that part. |
| 17:30:31 | <geekosaur> | with backward compatibility cited as the reason |
| 17:30:40 | <geekosaur> | since we'd just made a major release |
| 17:45:52 | <haskellbridge> | <Plume> Ok I can't seem to figure it out... |
| 17:45:52 | <haskellbridge> | I wonder if it's because the left_ptr cursor is propagated from the displayManager, but not the rest (e.g., xC_fleur) |
| 17:46:35 | <haskellbridge> | <Plume> If I run "xsetroot -cursor_name fleur" it would work just fine, but the grabbing and resizing cursors are still wrong. |
| 17:47:55 | <geekosaur> | what version of xmonad is nix giving you? |
| 17:49:47 | <haskellbridge> | <Plume> XMonad 0.18.0 |
| 17:50:15 | <haskellbridge> | <Plume> I wonder if I need to set the cursor right before XMonad starts? |
| 17:52:09 | <geekosaur> | generally yes, it's read during Xlib startup and most programs only catch such things during startup as a result |
| 17:52:52 | <geekosaur> | I'm going to be out doing errands for the next few hours |
| 17:54:10 | <haskellbridge> | <Plume> No problem, thank you for your help. |
| 17:54:11 | <haskellbridge> | Also I want to correct me saying I have the same problem as in issue 352. My cursor do change, they just don't follow the theme. |
| 17:55:50 | <haskellbridge> | <Plume> They change to the right shape, but wrong theme |
| 23:11:54 | × | todi quits (~todi@p57803331.dip0.t-ipconnect.de) (Ping timeout: 260 seconds) |
All times are in UTC on 2025-05-27.