2025/03/16

Newest at the top

2025-03-16 19:25:45 +0100econo_(uid147250@id-147250.tinside.irccloud.com)
2025-03-16 19:22:58 +0100euandreh(~Thunderbi@189.6.105.228) euandreh
2025-03-16 19:22:38 +0100euandreh(~Thunderbi@189.6.105.228) (Quit: euandreh)
2025-03-16 19:22:24 +0100 <davean> Thanks. I don't have much time to work on it but I do want to look
2025-03-16 19:19:16 +0100 <merijn> Seems to be present in HEAD too
2025-03-16 19:19:11 +0100 <merijn> I need to go for dinner, if you wanna reproduce it, the `unify` branch here shows the issue: https://github.com/merijn/broadcast-chan
2025-03-16 19:18:37 +0100 <davean> I do like how you split up the library
2025-03-16 19:18:36 +0100 <merijn> basically with multiple library components it builds docs for each that seem fine (well, it includes a txt file that uses <lib>:<sublib> in the filename which hackage rejects since it's not valid on windows)
2025-03-16 19:17:57 +0100 <davean> thats why I started taking a look
2025-03-16 19:17:52 +0100 <davean> That is interesting
2025-03-16 19:17:18 +0100 <merijn> davean: What's not nice is cabal racing my doc generation :p
2025-03-16 19:16:51 +0100 <davean> documentation and deception? Thats not nice!
2025-03-16 19:16:36 +0100 <merijn> davean: I'm a nice boy, so I generally upload source *AND* docs :p
2025-03-16 19:16:01 +0100 <davean> I thought you uploaded the source code. Thats my prefered docs anyway.
2025-03-16 19:15:12 +0100DigitteknohippieDigit
2025-03-16 19:13:37 +0100 <merijn> If they want docs, they can go fix cabal-install :p
2025-03-16 19:09:45 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 276 seconds)
2025-03-16 19:09:35 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-03-16 19:08:49 +0100euleritian(~euleritia@dynamic-176-006-136-106.176.6.pool.telefonica.de)
2025-03-16 19:05:53 +0100michalz(~michalz@185.246.207.203)
2025-03-16 19:05:24 +0100euleritian(~euleritia@ip5f5ad695.dynamic.kabel-deutschland.de) (Ping timeout: 246 seconds)
2025-03-16 19:04:44 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-16 19:04:03 +0100weary-traveler(~user@user/user363627) (Remote host closed the connection)
2025-03-16 19:01:41 +0100 <EvanR> it's open source. Who needs docs
2025-03-16 19:00:21 +0100 <merijn> welp, tough shit for users then, no docs for them :p
2025-03-16 18:53:44 +0100 <merijn> And haddock-project just seems to error out
2025-03-16 18:53:09 +0100 <merijn> I already tried that, but as usual it lies to me
2025-03-16 18:51:36 +0100ash3en(~Thunderbi@89.56.182.235) (Quit: ash3en)
2025-03-16 18:50:51 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2025-03-16 18:50:49 +0100 <EvanR> upgrade to chatGPT
2025-03-16 18:50:42 +0100 <EvanR> google smh
2025-03-16 18:47:05 +0100weary-traveler(~user@user/user363627) user363627
2025-03-16 18:45:51 +0100 <merijn> I'm sure *someone* has succesfully done this, but google is only turning up uselessly out of date result or results for the wrong topic
2025-03-16 18:45:20 +0100Digit(~user@user/digit) (Ping timeout: 252 seconds)
2025-03-16 18:45:10 +0100 <merijn> hmmm, manually fixing up the haddock file still doesn't seem to work. At least, the docs aren't visible on the hackage candidate
2025-03-16 18:44:00 +0100Digitteknohippie(~user@user/digit) Digit
2025-03-16 18:42:10 +0100Pixi(~Pixi@user/pixi) (Read error: Connection reset by peer)
2025-03-16 18:34:57 +0100 <merijn> anyone know what the txt file that `cabal haddock` generates is? Is it just a text representation of the documentation? If yes, how do I stop it from generating that, since it breaks things
2025-03-16 18:26:24 +0100notdabs(~Owner@2600:1700:69cf:9000:8c4a:1bad:bb61:8f8d)
2025-03-16 18:26:01 +0100notdabs(~Owner@2600:1700:69cf:9000:8c4a:1bad:bb61:8f8d) (Remote host closed the connection)
2025-03-16 18:23:30 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 248 seconds)
2025-03-16 18:21:13 +0100 <merijn> It also still includes file names that cause hackage to reject them
2025-03-16 18:21:04 +0100ash3en(~Thunderbi@89.56.182.235) ash3en
2025-03-16 18:20:49 +0100 <merijn> I have 3 library components and it seems to build docs for each and then write them out to the exact same path making it a race which docs you actually get
2025-03-16 18:20:08 +0100 <merijn> geekosaur: That does not seem fixed in HEAD
2025-03-16 18:19:21 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-16 18:16:01 +0100L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-03-16 18:13:47 +0100user363627(~user@user/user363627) (Remote host closed the connection)
2025-03-16 18:12:32 +0100 <merijn> I've been waiting for this glorious moment since, like, 2019 :p
2025-03-16 18:11:57 +0100 <merijn> because the gain from merging this back into 1 package is too great to postpone this over doc generation :p