Logs: liberachat/#xmonad
| 2021-10-31 19:57:01 | <L29Ah> | w/o picom |
| 2021-10-31 19:57:05 | <gehmehgeh> | ah |
| 2021-10-31 19:57:11 | <geekosaur> | uh |
| 2021-10-31 19:57:19 | <geekosaur> | you have segfaults? |
| 2021-10-31 19:57:19 | <L29Ah> | but picom is awesome because with --dbus you can use https://github.com/xmonad/xmonad-extras/pull/32 |
| 2021-10-31 19:57:23 | <gehmehgeh> | well I use a config file |
| 2021-10-31 19:57:29 | <L29Ah> | geekosaur: https://github.com/xmonad/xmonad/issues/328 |
| 2021-10-31 19:57:35 | <geekosaur> | oh |
| 2021-10-31 19:57:49 | <geekosaur> | I still want to see a gdb backtrace, for what good it'll do |
| 2021-10-31 19:58:20 | <L29Ah> | you didn't ask for it so i didn't preserve it :/ |
| 2021-10-31 19:58:46 | <gehmehgeh> | L29Ah: do you still have the core dump? |
| 2021-10-31 19:58:47 | <geekosaur> | may need to build xmonad with debugging turned on and/or system package debug symbols installed, for it to make sense |
| 2021-10-31 19:59:18 | <L29Ah> | gehmehgeh: even if i had, the binary is long gone |
| 2021-10-31 19:59:23 | <gehmehgeh> | ah, ok |
| 2021-10-31 19:59:47 | <geekosaur> | hm, I thought I had asked for it, but it looks like there's already at least a partial backtrace in that issue |
| 2021-10-31 20:02:03 | <geekosaur> | xmonad-0zi16zi99999zm1NVWfzz55W6QFvQzzDgdWm3D_XMonad.Core_$fLayoutClassLayoutWord64_.chandleMessage_info I think. (I need to write a z-code expander someday) |
| 2021-10-31 20:03:42 | <geekosaur> | eurgh, that looks bad. we should not be dumping core there. otoh you did say 9.0.1 and that's a pretty buggy ghc release |
| 2021-10-31 20:04:00 | <geekosaur> | 9.2.1 fixes most / hopefully all of the bugs |
| 2021-10-31 20:05:45 | <geekosaur> | (but we have an open pr fixing pattern match failures that 9.2.1 uncovers, so 8.10.7 may be preferable) |
| 2021-10-31 20:09:29 | <L29Ah> | ok i'll hop on 9.2.1 as soon as it's in Gentoo |
| 2021-10-31 20:10:59 | <geekosaur> | I'm kinda hard put to figure how it would be dumping core while evaluating a message unless it's either a ghc bug or undetected heap corruption from an earlier ffi call |
| 2021-10-31 20:11:40 | <geekosaur> | problem is, the latter are still soemwhat likely because xmonad/X11 very badly needs a full audit to make sure we're properly handling all possible X11 returns/errors |
| 2021-10-31 20:20:15 | <gehmehgeh> | L29Ah: Thanks again for sharing your picom settings :) |
| 2021-10-31 20:41:48 | × | catman quits (~catman@user/catman) (Read error: Connection reset by peer) |
| 2021-10-31 20:42:24 | → | mvk joins (~mvk@2607:fea8:5cc1:300::d3fb) |
| 2021-10-31 20:46:39 | → | banc- joins (banc@gateway/vpn/airvpn/banc) |
| 2021-10-31 20:47:14 | × | banc quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds) |
| 2021-10-31 20:47:21 | <L29Ah> | geekosaur: can i ask ghc for asan or smth? |
| 2021-10-31 20:48:15 | → | catman joins (~catman@user/catman) |
| 2021-10-31 20:49:19 | <geekosaur> | I don't think asan will work with the 2-stage allocator? |
| 2021-10-31 20:49:51 | <geekosaur> | and I doubt asan can make any sense of ghc's heap (or its stack, since it doesn't have one in the normal sense) |
| 2021-10-31 20:51:04 | <liskin> | note that the pattern match failures are just warnings, it all builds just fine without pedantic |
| 2021-10-31 20:51:42 | <liskin> | one needs to allow-newer: setlocale:base, hsc2hs:base, though |
| 2021-10-31 20:52:34 | <geekosaur> | wonder how hard it would be to allow xmonad or -contrib to use head.hackage |
| 2021-10-31 20:53:07 | <liskin> | probably a single line in cabal.haskell-ci? |
| 2021-10-31 20:53:45 | <liskin> | oh, head.hackage is something else |
| 2021-10-31 20:54:14 | <geekosaur> | right, it's a set of patches used to build hackage packages with development ghc versions |
| 2021-10-31 20:54:31 | <geekosaur> | think it's part of the ghc repo |
| 2021-10-31 20:55:23 | <liskin> | still, haskell-ci should just handle that |
| 2021-10-31 21:01:16 | → | mestre joins (~mestre@191.177.175.57) |
| 2021-10-31 21:19:37 | × | alternateved quits (~user@staticline-31-183-149-3.toya.net.pl) (Remote host closed the connection) |
| 2021-10-31 21:52:24 | × | gehmehgeh quits (~user@user/gehmehgeh) (Quit: Leaving) |
| 2021-10-31 21:58:53 | × | mestre quits (~mestre@191.177.175.57) (Quit: Lost terminal) |
| 2021-10-31 22:01:14 | <liskin> | oh crap, ppOrder = \(_:_:windowTitle:_) -> … now triggers Pattern match(es) are non-exhaustive :-( |
| 2021-10-31 22:01:39 | <liskin> | up until now it felt like these are maybe useful warnings, but this is just ugly :-/ |
| 2021-10-31 22:01:46 | <liskin> | what a waste of time |
| 2021-10-31 22:03:46 | <geekosaur> | https://github.com/geekosaur/xmonad.hs/blob/pyanfar/xmonad.hs#L277-L279 |
| 2021-10-31 22:08:11 | <liskin> | geekosaur: thx |
| 2021-10-31 22:08:27 | <liskin> | this is way better than anything I was going to come up with :-) |
| 2021-10-31 22:09:18 | <geekosaur> | well, I meant that more as in "but that pattern *can* in fact not match, for unknown reasons" |
| 2021-10-31 22:09:31 | <geekosaur> | or at least I was never able to figure them out |
| 2021-10-31 22:10:10 | <liskin> | with dynamicLogString it most certainly can not |
| 2021-10-31 22:10:12 | <geekosaur> | *one* of them might be because I was firing logHook off from startupHook and maybe the layoutHook hadn't done anything yet. but the other three? |
| 2021-10-31 22:10:44 | <liskin> | I mean, with dynamicLogString being the only caller of ppOrder |
| 2021-10-31 22:10:54 | <liskin> | which isn't guaranteed in any way |
| 2021-10-31 22:10:58 | <liskin> | so… whatever :-) |
| 2021-10-31 22:15:45 | × | mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2021-10-31 22:31:15 | → | humky_ joins (~humky@user/humky) |
| 2021-10-31 22:33:26 | × | humky quits (~humky@user/humky) (Ping timeout: 245 seconds) |
| 2021-10-31 22:36:42 | × | humky_ quits (~humky@user/humky) (Remote host closed the connection) |
| 2021-10-31 22:36:58 | → | humky joins (~humky@user/humky) |
| 2021-10-31 22:42:42 | → | alternateved joins (~user@staticline-31-183-149-3.toya.net.pl) |
| 2021-10-31 22:51:14 | → | humky_ joins (~humky@user/humky) |
| 2021-10-31 22:53:42 | × | humky quits (~humky@user/humky) (Ping timeout: 260 seconds) |
| 2021-10-31 23:07:31 | × | humky_ quits (~humky@user/humky) (Quit: Leaving) |
| 2021-10-31 23:09:16 | → | gruntsplatter joins (~sogens@gateway/vpn/pia/sogens) |
| 2021-10-31 23:12:49 | × | seschwar quits (~seschwar@user/seschwar) (Quit: :wq) |
| 2021-10-31 23:15:02 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
| 2021-10-31 23:15:22 | → | geekosaur joins (~geekosaur@xmonad/geekosaur) |
| 2021-11-01 00:33:59 | × | alternateved quits (~user@staticline-31-183-149-3.toya.net.pl) (Ping timeout: 264 seconds) |
| 2021-11-01 00:46:46 | → | electr0n joins (~electr0n@about/security/founder/electr0n) |
| 2021-11-01 01:00:21 | → | humky joins (~humky@user/humky) |
| 2021-11-01 01:33:10 | → | trillp joins (~trillp@69.233.98.238) |
| 2021-11-01 01:41:42 | × | Extropy quits (~extropy@gateway/tor-sasl/extropy) (Ping timeout: 276 seconds) |
| 2021-11-01 01:44:34 | → | Extropy joins (~extropy@gateway/tor-sasl/extropy) |
| 2021-11-01 01:45:30 | <FOSSHuman[m]> | Hello everyone. I have been using X.A.UpdatePointer, and since I have it set to move the mouse pointer to the exact bottom right of every window; When a floating window pops up, the pointer cannot "escape" the floating window, it is fine with normal tiled windows, but the fact that the pointer feels constrained to within the floating window, it makes the experience strange and feel constricting (like: I HAVE to do the thing in this |
| 2021-11-01 01:45:30 | <FOSSHuman[m]> | dialogue RIGHT NOW), anyone suggest a fix to this?? |
| 2021-11-01 01:46:34 | <FOSSHuman[m]> | * in this floating dialogue RIGHT |
| 2021-11-01 01:48:06 | <FOSSHuman[m]> | But I guess it does help with focus lol, to stop me from procrastinating and looking at reddit/HN while an important floating dialogue pops up lol... |
| 2021-11-01 01:49:32 | <FOSSHuman[m]> | TLDR: X.A.UpdatePointer does not allow the pointer to "escape" certain floating dialogues. |
| 2021-11-01 01:52:07 | <FOSSHuman[m]> | I have commented out X.A.UpdatePointer for the meantime, and I'm just using the default XMonad mouse window focus behaviour.. |
| 2021-11-01 01:53:51 | × | mvk quits (~mvk@2607:fea8:5cc1:300::d3fb) (Ping timeout: 245 seconds) |
| 2021-11-01 01:56:25 | × | catman quits (~catman@user/catman) (Read error: Connection reset by peer) |
| 2021-11-01 01:56:27 | <FOSSHuman[m]> | > `TLDR: X.A.UpdatePointer does not allow the pointer to "escape" certain floating dialogues.` The pointer just returns to the coordinates (in my case, the bottom right of the window)... |
| 2021-11-01 01:56:29 | <lambdabot> | <hint>:1:1: error: parse error on input ‘`’ |
| 2021-11-01 02:04:40 | ← | ArgoLargo[m] parts (~argolargo@2001:470:69fc:105::1:16b1) () |
| 2021-11-01 02:09:06 | → | catman joins (~catman@user/catman) |
| 2021-11-01 02:19:42 | → | mvk joins (~mvk@2607:fea8:5cc1:300::d3fb) |
| 2021-11-01 02:47:44 | × | mvk quits (~mvk@2607:fea8:5cc1:300::d3fb) (Quit: Konversation terminated!) |
| 2021-11-01 02:47:47 | × | Hash quits (~stoned@is.coding.when.stoned.io) (Ping timeout: 264 seconds) |
| 2021-11-01 03:04:22 | × | banc- quits (banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds) |
| 2021-11-01 03:24:10 | → | banc joins (banc@gateway/vpn/airvpn/banc) |
| 2021-11-01 03:26:27 | × | catman quits (~catman@user/catman) (Read error: Connection reset by peer) |
| 2021-11-01 03:47:18 | × | thunderrd quits (~thunderrd@183.182.110.1) (Ping timeout: 260 seconds) |
| 2021-11-01 03:49:02 | → | catman joins (~catman@user/catman) |
| 2021-11-01 03:52:40 | × | Extropy quits (~extropy@gateway/tor-sasl/extropy) (Quit: WeeChat 3.3) |
| 2021-11-01 03:54:43 | → | Hash joins (~stoned@is.coding.when.stoned.io) |
| 2021-11-01 04:03:57 | × | darkstarx quits (~darkstard@2601:1c2:300:c8a0::6c32) (Quit: Leaving) |
| 2021-11-01 04:11:59 | → | darkstardevx joins (~darkstard@2601:1c2:300:c8a0::6c32) |
| 2021-11-01 04:13:49 | × | darkstardevx quits (~darkstard@2601:1c2:300:c8a0::6c32) (Remote host closed the connection) |
All times are in UTC.