2025/04/04

Newest at the top

2025-04-04 08:23:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-04-04 08:21:07 +0200Unicorn_Princess(~Unicorn_P@user/Unicorn-Princess/x-3540542) Unicorn_Princess
2025-04-04 08:20:00 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 246 seconds)
2025-04-04 08:19:24 +0200hattckory(~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 260 seconds)
2025-04-04 08:19:07 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-04 08:14:12 +0200 <haskellbridge> <Liamzee> "developed by people who thought the best part of Rust was fighting with the borrow checker"
2025-04-04 08:13:59 +0200 <haskellbridge> <Liamzee> then
2025-04-04 08:13:48 +0200 <haskellbridge> <Liamzee> "wow, linear haskell is a wonderful idea"
2025-04-04 08:13:43 +0200 <haskellbridge> <Liamzee> i guess i love my experience with linear haskell being, every few months:
2025-04-04 08:12:12 +0200hattckory(~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca)
2025-04-04 08:08:13 +0200ft(~ft@p508db463.dip0.t-ipconnect.de) (Quit: leaving)
2025-04-04 08:07:18 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds)
2025-04-04 08:02:29 +0200fp1(~Thunderbi@2001:708:20:1406::1370) fp
2025-04-04 08:02:21 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-04 08:00:19 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-04-04 07:55:21 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-04 07:44:36 +0200emmanuelux(~emmanuelu@user/emmanuelux) (Quit: au revoir)
2025-04-04 07:44:01 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-04-04 07:37:19 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-04 07:29:31 +0200 <sim590> It seems like cabal decided to use the wrong NetworkState file in the root directory (that didn't have the constructor) even though `hs-source-dirs:` for `habanga-core` said `src/core`. So like if you have files in subdirectories, it's possible cabal/ghc confuses files in the root directories with files in the subdirectories. Seems like a bug.
2025-04-04 07:28:50 +0200ERR0R157(~ERR0R157@user/ERR0R157) (Remote host closed the connection)
2025-04-04 07:26:36 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-04-04 07:24:25 +0200 <sim590> Ah gawd. It seems like my Vim decided to save the file in the root directory of the repo instead of it's usual path and I,ve been editing that file since. Damn.
2025-04-04 07:22:15 +0200weary-traveler(~user@user/user363627) (Remote host closed the connection)
2025-04-04 07:22:11 +0200 <sim590> OK. There's clearly something. I'm not sure what it is yet. The file seems to be OK on disk, but git says it's "untracked". Even though, I committed it...
2025-04-04 07:21:57 +0200 <haskellbridge> <Liamzee> is there a simpler way to do (unur . move)?
2025-04-04 07:21:32 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-04 07:21:05 +0200 <c_wraith> ... which is surprisingly common
2025-04-04 07:20:51 +0200 <c_wraith> That sounds way more confusing than any time I've saved to the wrong file.
2025-04-04 07:20:08 +0200 <sim590> I think I was editing the file in the Git staging area. Because of fugitive.vim.
2025-04-04 07:19:44 +0200 <sim590> Fuc
2025-04-04 07:19:42 +0200 <sim590> Oh.
2025-04-04 07:19:20 +0200 <sim590> Yes :D
2025-04-04 07:19:12 +0200 <c_wraith> Ok, getting into real "just in case" territory - are you sure you've saved the change?
2025-04-04 07:17:54 +0200 <sim590> It's in NetworkState
2025-04-04 07:17:47 +0200 <sim590> it does compile it.. :/
2025-04-04 07:17:41 +0200gmg(~user@user/gehmehgeh) gehmehgeh
2025-04-04 07:17:40 +0200 <sim590> c_wraith: here's what I got: https://paste.debian.net/1367361/
2025-04-04 07:17:06 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-04-04 07:16:59 +0200gmg(~user@user/gehmehgeh) (Remote host closed the connection)
2025-04-04 07:16:42 +0200 <c_wraith> but I suppose you know what I meant
2025-04-04 07:16:34 +0200 <c_wraith> oh, I had that backwards. -core is the one that might not be recompiling
2025-04-04 07:15:30 +0200 <sim590> That would explain.
2025-04-04 07:15:06 +0200 <sim590> Let me check.
2025-04-04 07:15:03 +0200 <sim590> Oh I see.
2025-04-04 07:14:48 +0200 <c_wraith> Did it actually compile that component during the recompile?
2025-04-04 07:14:24 +0200 <sim590> Same error.
2025-04-04 07:14:21 +0200 <sim590> Then, I recompiled.
2025-04-04 07:14:18 +0200 <sim590> I did a full `v2-clean`.
2025-04-04 07:14:07 +0200 <c_wraith> did the habanga-tui component get recompiled?