2026/02/12

Newest at the top

2026-02-12 05:40:44 +0100Guest56(~Guest56@155.2.191.86) (Quit: Client closed)
2026-02-12 05:39:04 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-02-12 05:38:38 +0100messewix(~jmc@user/messewix) (Quit: Konversation terminated!)
2026-02-12 05:37:40 +0100lisbeths(uid135845@id-135845.lymington.irccloud.com) lisbeths
2026-02-12 05:34:34 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 05:30:55 +0100wickedjargon(~user@2605:8d80:5431:6065:7b8a:6513:6c7e:c79c) wickedjargon
2026-02-12 05:25:30 +0100weary-traveler(~user@user/user363627) user363627
2026-02-12 05:23:39 +0100 <jreicher> Does the language server get just as confused fronted by VS code?
2026-02-12 05:23:14 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-02-12 05:20:58 +0100jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 260 seconds)
2026-02-12 05:18:37 +0100 <feetwind> yeah, it's part of the ritual when it's not an obvious build error hls can't get past for some reason. the holy incantations C-g C-g C-g C-g , eglot-shutdown-all, cabal clean, rm -rf ~/.cache/hie-bios
2026-02-12 05:16:31 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 05:05:29 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-12 05:04:28 +0100ft(~ft@p4fc2afab.dip0.t-ipconnect.de) ft
2026-02-12 05:02:43 +0100ft(~ft@p508db4c0.dip0.t-ipconnect.de) (Ping timeout: 264 seconds)
2026-02-12 05:01:49 +0100thaumavorio(~thaumavor@thaumavor.io) thaumavorio
2026-02-12 05:01:09 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 05:00:31 +0100thaumavorio(~thaumavor@thaumavor.io) (Quit: ZNC 1.8.2 - https://znc.in)
2026-02-12 04:53:01 +0100Guest56(~Guest56@155.2.191.86)
2026-02-12 04:50:25 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-02-12 04:45:47 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 04:41:00 +0100rekahsoft(~rekahsoft@bras-base-orllon1103w-grc-20-76-67-111-168.dsl.bell.ca) (Remote host closed the connection)
2026-02-12 04:34:54 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-02-12 04:31:58 +0100Square(~Square4@user/square) (Ping timeout: 260 seconds)
2026-02-12 04:30:24 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 04:25:52 +0100Square(~Square4@user/square) Square
2026-02-12 04:25:12 +0100Square(~Square4@user/square) (Remote host closed the connection)
2026-02-12 04:19:17 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2026-02-12 04:17:09 +0100td_(~td@i5387091F.versanet.de) td_
2026-02-12 04:15:16 +0100td_(~td@i5387093E.versanet.de) (Ping timeout: 246 seconds)
2026-02-12 04:15:03 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 04:05:25 +0100machinedgod(~machinedg@d75-159-126-101.abhsia.telus.net) (Ping timeout: 264 seconds)
2026-02-12 04:00:39 +0100 <geekosaur> occasionally clearing hie-bios's cache (~/.cache/hie-bios) helps, if it gets corrupted then things may get rebuilt unexpectedly
2026-02-12 03:57:50 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-12 03:54:06 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-02-12 03:53:24 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 03:49:49 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2026-02-12 03:47:07 +0100prdak(~Thunderbi@user/prdak) (Ping timeout: 264 seconds)
2026-02-12 03:42:21 +0100prdak(~Thunderbi@user/prdak) prdak
2026-02-12 03:41:57 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds)
2026-02-12 03:35:21 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-02-12 03:33:56 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2026-02-12 03:33:07 +0100 <feetwind> `cabal repl all --enable-multi-repl` seemingly works as it ought to, not trying to rebuild transitive deps of each target, even if one's build fails along the way. that's pretty useful actually even tho multi repl is limited
2026-02-12 03:27:23 +0100 <haskellbridge> <sm> and would be easier to troubleshoot outside of HLS
2026-02-12 03:27:09 +0100 <haskellbridge> <sm> if you can figure out what it's doing, maybe you can test the same commands at cli and see if there's excessive rebuilding going on or something. This is pretty common
2026-02-12 03:25:25 +0100 <feetwind> but otoh nice to not have such a long build if `subcmd` is just a little test script or whatever. ah well
2026-02-12 03:24:28 +0100 <feetwind> i will see if just having lots of hie components is behind very long waits sometimes, probably nicer to have my app as `app subcmd ...`
2026-02-12 03:24:17 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-02-12 03:22:50 +0100 <haskellbridge> <sm> it's not super robust. But it's valuable enough to be worth babysitting
2026-02-12 03:22:03 +0100 <feetwind> yeah that's what i end up doing, but then that was what hls was supposed to help with in the first place ๎นป