2024/11/10

Newest at the top

2024-11-10 23:12:39 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-11-10 23:11:22 +0100CoolMa7(~CoolMa7@95.91.137.87) (Quit: My Mac has gone to sleep. ZZZzzz…)
2024-11-10 23:07:16 +0100halloy6033(~halloy603@a89-152-101-97.cpe.netcabo.pt)
2024-11-10 23:05:40 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-10 23:00:51 +0100ljdarj1ljdarj
2024-11-10 23:00:49 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2024-11-10 22:58:33 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2024-11-10 22:56:27 +0100Guest30(~Guest30@2a01:cb19:a0f:df00:9123:e7e6:8a15:d31) (Client Quit)
2024-11-10 22:55:06 +0100Guest30(~Guest30@2a01:cb19:a0f:df00:9123:e7e6:8a15:d31)
2024-11-10 22:54:33 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds)
2024-11-10 22:52:28 +0100anpad(~pandeyan@user/anpad) anpad
2024-11-10 22:49:53 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-10 22:47:59 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2024-11-10 22:47:55 +0100pandeyan(~pandeyan@135-180-52-227.fiber.dynamic.sonic.net) (Quit: ZNC 1.8.2 - https://znc.in)
2024-11-10 22:39:02 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-11-10 22:37:52 +0100CoolMa7(~CoolMa7@95.91.137.87) CoolMa7
2024-11-10 22:37:02 +0100lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 255 seconds)
2024-11-10 22:34:05 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-10 22:29:44 +0100michalz(~michalz@185.246.207.221)
2024-11-10 22:24:26 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2024-11-10 22:23:39 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-11-10 22:18:18 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-10 22:14:47 +0100tv(~tv@user/tv) tv
2024-11-10 22:14:05 +0100rvalue(~rvalue@user/rvalue) (Ping timeout: 255 seconds)
2024-11-10 22:12:33 +0100tv(~tv@user/tv) (Read error: Connection reset by peer)
2024-11-10 22:09:33 +0100xdminsy(~xdminsy@117.147.71.147) (Ping timeout: 265 seconds)
2024-11-10 22:09:22 +0100rvalue(~rvalue@user/rvalue) rvalue
2024-11-10 22:07:29 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-11-10 22:07:25 +0100alexherbo2(~alexherbo@2a02-8440-3105-b12d-6cb6-6a29-cc7c-8727.rev.sfr.net) (Remote host closed the connection)
2024-11-10 22:05:25 +0100ystael(~ystael@user/ystael) (Ping timeout: 248 seconds)
2024-11-10 22:02:39 +0100 <geekosaur> but it doesn't sound like this, it involves Prelude
2024-11-10 22:02:33 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-11-10 22:02:25 +0100 <geekosaur> mm, the manual does mention some ghci magic involving *-modules
2024-11-10 22:02:10 +0100 <tomsmeding> I leave that to cabal and HLS people to figure out
2024-11-10 22:01:58 +0100 <tomsmeding> I have no clue what's going on with multi-unit stuff :)
2024-11-10 22:01:40 +0100 <tomsmeding> I don't think this is a cabal issue
2024-11-10 22:01:29 +0100 <geekosaur> ther shenanigans are worse without multi-repl since cabal tries to sort-of simulate it
2024-11-10 22:01:22 +0100 <haskellbridge> <sm> ok.
2024-11-10 22:01:13 +0100 <tomsmeding> sm: I didn't try, but the behaviour that I dislike with `cabal repl` is completely reproduced with `ghci A.hs B.hs`
2024-11-10 22:00:48 +0100 <haskellbridge> <sm> tomsmeding: did you get cabal to show its ghci command ?
2024-11-10 22:00:39 +0100 <tomsmeding> (I am aware of the existence of intense shenanigans with multi-unit repls, and I don't want to go there)
2024-11-10 22:00:21 +0100 <tomsmeding> so at least for the simple case of multiple modules from the same unit, ghci doesn't seem to have any problems
2024-11-10 21:59:54 +0100 <tomsmeding> well `ghci A.hs B.hs` works perfectly well for me!
2024-11-10 21:59:30 +0100 <tomsmeding> geekosaur: of course, I ~always go through `cabal repl`, so the discussion about plain ghci is academic and/or to figure out what's really happening underneath
2024-11-10 21:59:29 +0100 <haskellbridge> <sm> agreed on complex, ghci's semantics and cabal's are each complicated on their own
2024-11-10 21:59:14 +0100 <geekosaur> (trying to make ghci deal nicely with multiple modules when it generally doesn't so much)
2024-11-10 21:58:59 +0100xdminsy(~xdminsy@117.147.71.147) xdminsy
2024-11-10 21:58:57 +0100 <tomsmeding> except for this stupid :r behaviour :p
2024-11-10 21:58:52 +0100 <tomsmeding> I recall at least skimming the manual on this, and learning about the details of the syntax of `:m` and finding it useful
2024-11-10 21:58:42 +0100 <geekosaur> I don't have a lot that doesn't require me to go through `cabal repl` and deal with whatever it's doing, which is moderately complex