2023-11-20 00:27:44 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Ping timeout: 268 seconds) |
2023-11-20 00:27:47 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 256 seconds) |
2023-11-20 00:40:51 +0100 | <liskin> | I thought turning ShrinkMaster into ExpandMaster and vice versa would be sane-ish |
2023-11-20 00:41:22 +0100 | <liskin> | But it does make the assumption that it's a horizontal shrinking |
2023-11-20 00:41:33 +0100 | <liskin> | Which is not true for all layouts I guess |
2023-11-20 00:42:18 +0100 | <liskin> | Anyway, one can easily make a layout modifier that remaps the messages, so... |
2023-11-20 00:46:18 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
2023-11-20 00:46:18 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
2023-11-20 00:46:18 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) |
2023-11-20 00:47:27 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
2023-11-20 02:52:00 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) (Quit: ZNC - https://znc.in) |
2023-11-20 02:56:42 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) |
2023-11-20 03:15:25 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) (Quit: ZNC - https://znc.in) |
2023-11-20 03:20:09 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) |
2023-11-20 04:16:51 +0100 | td_ | (~td@i53870935.versanet.de) (Ping timeout: 256 seconds) |
2023-11-20 04:18:47 +0100 | td_ | (~td@i5387090F.versanet.de) |
2023-11-20 04:42:29 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
2023-11-20 04:45:07 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) |
2023-11-20 07:24:42 +0100 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) |
2023-11-20 07:35:07 +0100 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Quit: Time to sleep!) |
2023-11-20 09:08:10 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 255 seconds) |
2023-11-20 09:09:49 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) (Ping timeout: 256 seconds) |
2023-11-20 09:29:38 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
2023-11-20 09:29:38 +0100 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
2023-11-20 09:29:38 +0100 | xmonadtrack | (~xmonadtra@user/geekosaur/bot/xmonadtrack) |
2023-11-20 11:32:22 +0100 | haskellbridge | (~haskellbr@069-135-003-034.biz.spectrum.com) |
2023-11-20 13:07:17 +0100 | haskl | (~haskl@user/haskl) (Remote host closed the connection) |
2023-11-20 13:07:34 +0100 | haskl | (~haskl@user/haskl) |
2023-11-20 13:08:39 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:8c15:d658:f6c0:b840) |
2023-11-20 13:42:43 +0100 | ft | (~ft@mue-88-130-106-120.dsl.tropolys.de) (Quit: leaving) |
2023-11-20 14:23:56 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:8c15:d658:f6c0:b840) (Ping timeout: 268 seconds) |
2023-11-20 14:25:47 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:3334:bb1d:62ea:76e2) |
2023-11-20 15:56:55 +0100 | deepy | (deepy@user/deepy) (Read error: Connection reset by peer) |
2023-11-20 15:57:37 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:3334:bb1d:62ea:76e2) (Ping timeout: 246 seconds) |
2023-11-20 15:58:04 +0100 | deepy | (deepy@user/deepy) |
2023-11-20 16:05:01 +0100 | deepy | (deepy@user/deepy) (Read error: Connection reset by peer) |
2023-11-20 16:19:50 +0100 | deepy | (deepy@user/deepy) |
2023-11-20 16:50:35 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:30:6015:6959:7134) |
2023-11-20 18:11:59 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:30:6015:6959:7134) (Ping timeout: 256 seconds) |
2023-11-20 18:13:36 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:e42:7f5f:7c38:1b67) |
2023-11-20 18:35:13 +0100 | <haskellbridge> | <yoggurt> hey, after I resolve issues with PR's should I ping or reply in the thread? I don't want to rush anyone to merge it. Just wondering what's the procedure |
2023-11-20 18:36:31 +0100 | <geekosaur> | It would probably help; we don't get notified for some things |
2023-11-20 18:43:01 +0100 | <haskellbridge> | <yoggurt> ok I'll do so, just didn't want to be annoying |
2023-11-20 18:45:28 +0100 | <Solid> | Yes pinging us is totally fine :) |
2023-11-20 18:53:33 +0100 | <geekosaur> | in particular, if you use "draft" state while working on it and turn it off when it's ready, we still get notified about draft commits *and* it doesn't tell us when it's set to "ready to review", which is somewhat annoying |
2023-11-20 19:48:28 +0100 | <Solid> | [Leary]: why don't we have a flake.lock file for either repo, btw? I thought that this was kind of important for how nix wants to work |
2023-11-20 20:10:28 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:e42:7f5f:7c38:1b67) (Ping timeout: 256 seconds) |
2023-11-20 20:20:32 +0100 | <xmonadtrack> | xmonad Tony Zorman * v0.17.2-105-g8421b10: flake: Allow users to modify the dev shell (43 minutes ago, 1 file, 6+ 2-) https://github.com/xmonad/xmonad/commit/8421b100dd93 |
2023-11-20 20:31:01 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:b67b:de87:7872:e69f) |
2023-11-20 20:59:36 +0100 | <[Leary]> | Solid: I'm not 100% on this, but I think root/executable flakes should include lockfiles, while child-node/library flakes should not, for various reasons. I'm treating xmonad/-contrib as the latter. |
2023-11-20 21:30:31 +0100 | _qw | (~eqw@31.134.178.99) (Remote host closed the connection) |
2023-11-20 22:15:08 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:b67b:de87:7872:e69f) (Ping timeout: 256 seconds) |
2023-11-20 22:50:20 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) (Quit: ZNC - https://znc.in) |
2023-11-20 22:53:21 +0100 | alp_ | (~alp@2001:861:e3d6:8f80:3e0c:4d1b:db32:9e54) |
2023-11-20 22:54:09 +0100 | todi | (~todi@p4fd1a3e6.dip0.t-ipconnect.de) |
2023-11-20 23:15:56 +0100 | ft | (~ft@p508db3bc.dip0.t-ipconnect.de) |
2023-11-20 23:59:15 +0100 | <haskellbridge> | <yoggurt> wasn't aware but that makes a lot of sense. When I used xmonad as an input into my NixOS it came with a lot of flakes |