2026/01/06

2026-01-06 00:10:51 +0100zawaken(~zawaken@user/zawaken) (Quit: ZNC - https://znc.in)
2026-01-06 08:11:46 +0100vanvik(~vanvik@143.110.100.4) (Quit: Later)
2026-01-06 08:12:53 +0100vanvik(~vanvik@143.110.100.4) vanvik
2026-01-06 12:17:50 +0100ml|(~ml|@user/ml/x-5298235) (Ping timeout: 256 seconds)
2026-01-06 12:31:51 +0100ml|(~ml|@user/ml/x-5298235) ml|
2026-01-06 12:38:29 +0100mc47(~yecinem@xmonad/TheMC47) mc47
2026-01-06 12:42:16 +0100 <mc47> hey! I want to get XMonad.Util.StickyWindows merged, but it currently relies on the "mvdt" branches. The issue with the current implementation is that I'm calling windows to shift the sticky windows and unfocus them whenever the workspace changes, which calls the loghook. Is there a way around calling windows?
2026-01-06 12:52:24 +0100 <mc47> nevermind... I can't believe I couldn't figure out a workaround earlier...
2026-01-06 12:59:59 +0100ChubaDuba(~ChubaDuba@46.147.219.139) ChubaDuba
2026-01-06 13:01:15 +0100Miroboru(~myrvoll@188.113.115.67) (Quit: Lost terminal)
2026-01-06 13:02:05 +0100ChubaDuba(~ChubaDuba@46.147.219.139) (Client Quit)
2026-01-06 13:58:03 +0100mkoskar(mkoskar@user/mkoskar) (Quit: mkoskar)
2026-01-06 13:58:13 +0100mkoskar(mkoskar@user/mkoskar) mkoskar
2026-01-06 14:01:02 +0100 <haskellbridge> <Solid> Mh, I wonder, will GH automatically squash fixup commits if I merge the branch
2026-01-06 14:01:47 +0100 <haskellbridge> <Solid> …no, no it will not
2026-01-06 14:02:18 +0100 <haskellbridge> <Solid> sorry for the slightly worse history
2026-01-06 14:03:26 +0100 <haskellbridge> <Solid> Also, I think I'm feeling a release on the weekend (if I get to review #807 until then)
2026-01-06 15:03:31 +0100 <mc47> It will not, I've been bitten by it often at work :D You have to select squash in the dropdown. No biggie
2026-01-06 15:28:54 +0100mc47(~yecinem@xmonad/TheMC47) (Remote host closed the connection)
2026-01-06 16:29:06 +0100 <liskin> No! Squash will do something else - it will squash everything.
2026-01-06 16:41:27 +0100 <haskellbridge> <Solid> Yeah exactly
2026-01-06 16:41:43 +0100 <haskellbridge> <Solid> I guess in this case we're talking about one commit so it wouldn't have mattered
2026-01-06 16:42:09 +0100 <haskellbridge> <Solid> But in general I don't like squashing if someone actually cared enough to write proper commit messages
2026-01-06 16:46:05 +0100 <haskellbridge> <Solid> I'm almost tempted to just add -Wno-incomplete-record-selectors
2026-01-06 16:46:06 +0100 <haskellbridge> <Solid> to the "pedantic" flag
2026-01-06 16:48:56 +0100 <liskin> +1 on no-i-r-s
2026-01-06 16:49:25 +0100 <liskin> (+1 on no-irs and no-ice probably as well lol)
2026-01-06 16:51:01 +0100 <haskellbridge> <Solid> :D
2026-01-06 17:56:08 +0100 <haskellbridge> <geekosaur (@geekosaur:matrix.org)> I'm under the impression that autosquash is considered bad now fwiw
2026-01-06 18:09:08 +0100 <liskin> Wat
2026-01-06 18:09:30 +0100 <liskin> (I mean seriously - wat. Citation needed.)
2026-01-06 18:29:42 +0100 <haskellbridge> <geekosaur (@geekosaur:matrix.org)> I haven't found any aside from Mergify documentation (used by cabal) claiming it was bad and nobody should ever use it. Hence "impression"
2026-01-06 20:10:46 +0100 <liskin> Okay that doesn't seem worth me googling it. Do feel free to send a link though