Newest at the top
| 2025-01-31 14:35:19 +0100 | zmt01 | (~zmt00@user/zmt00) (Ping timeout: 260 seconds) |
| 2025-01-31 14:32:24 +0100 | tabaqui1 | (~root@87.200.129.102) tabaqui |
| 2025-01-31 14:31:52 +0100 | swamp_ | (~zmt00@user/zmt00) zmt00 |
| 2025-01-31 14:31:30 +0100 | <haskellbridge> | <sm> what about https://hackage.haskell.org/package/rapid-0.1.5.3/docs/Rapid.html |
| 2025-01-31 14:31:14 +0100 | CiaoSen | (~Jura@2a05:5800:263:8800:ca4b:d6ff:fec1:99da) (Ping timeout: 260 seconds) |
| 2025-01-31 14:30:24 +0100 | p3n | (~p3n@2a00:19a0:3:7c:0:d9c6:7cf6:1) (Quit: ZNC 1.9.1 - https://znc.in) |
| 2025-01-31 14:29:52 +0100 | <haskellbridge> | <sm> or up enter, as you say |
| 2025-01-31 14:29:15 +0100 | <haskellbridge> | <sm> it means I can just CTRL-p, enter after a change |
| 2025-01-31 14:29:01 +0100 | alexherbo2 | (~alexherbo@2a02-8440-3504-8116-f81b-81aa-4344-3e67.rev.sfr.net) (Remote host closed the connection) |
| 2025-01-31 14:28:25 +0100 | <haskellbridge> | ... long message truncated: https://kf8nh.com/_heisenbridge/media/kf8nh.com/sCYnuCtwPTknTRbDePLKlYOX/yxjBbcu9HSA (3 lines) |
| 2025-01-31 14:28:25 +0100 | <haskellbridge> | <sm> kaol: you might like this small improvement in .ghci, I find it very useful: |
| 2025-01-31 14:27:39 +0100 | <haskellbridge> | <sm> love it |
| 2025-01-31 14:27:35 +0100 | <haskellbridge> | <sm> ghcid is a hack of the gods, then :) |
| 2025-01-31 14:19:59 +0100 | AlexZenon_2 | AlexZenon |
| 2025-01-31 14:17:44 +0100 | jespada | (~jespada@2800:a4:2215:4d00:20a9:6cd:d7c4:a65f) jespada |
| 2025-01-31 14:14:55 +0100 | jespada | (~jespada@2800:a4:2213:dd00:8c24:32fa:8fb8:ea12) (Ping timeout: 244 seconds) |
| 2025-01-31 14:09:02 +0100 | <kaol> | Give me something that integrates with the repl. |
| 2025-01-31 14:08:23 +0100 | <kaol> | ghcid is the hack. |
| 2025-01-31 14:08:13 +0100 | <geekosaur> | that sounds like a hacky way to reinvent ghcid/ghciwatch |
| 2025-01-31 14:08:08 +0100 | <kaol> | No wait, up enter is only relevat if I use history. |
| 2025-01-31 14:07:09 +0100 | <kaol> | I'm thinking of using inotify to use xdotool to send that :r up enter. Then I would have the code loaded in it already and not have to look at two windows and still do :r up enter. |
| 2025-01-31 14:06:39 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
| 2025-01-31 14:06:07 +0100 | <__monty__> | Ah, carry on. |
| 2025-01-31 14:05:08 +0100 | <geekosaur> | that was what started this thread |
| 2025-01-31 14:04:17 +0100 | <__monty__> | You can invert the order of errors reported by GHC FYI. |
| 2025-01-31 14:03:58 +0100 | <haskellbridge> | <sm> ghcid gets its own window, of course |
| 2025-01-31 14:03:34 +0100 | <kaol> | ghcid doesn't really fit my use patterns. Once I get it to compile I usually want to try out a few things with my new functions in the repl. |
| 2025-01-31 14:02:30 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-01-31 13:57:16 +0100 | <tomsmeding> | kaol: this is what ghcid does correctly, it shows only the top screenful of errors :p |
| 2025-01-31 13:56:21 +0100 | alexherbo2 | (~alexherbo@2a02-8440-3504-8116-f81b-81aa-4344-3e67.rev.sfr.net) alexherbo2 |
| 2025-01-31 13:55:48 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac |
| 2025-01-31 13:55:40 +0100 | <dminuoso> | I'm not impressed. |
| 2025-01-31 13:55:32 +0100 | <dminuoso> | And the Haskell Report has no guidance on the behavior of fromInteger either. |
| 2025-01-31 13:54:50 +0100 | <haskellbridge> | <sm> kaol: I can't quite relate to that. I feel the first error is more likely to be the causative one, and I am generally using either VS code or ghcid which shows it |
| 2025-01-31 13:54:08 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-01-31 13:53:43 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
| 2025-01-31 13:52:15 +0100 | <dminuoso> | fromInteger i = W8# (wordToWord8# (integerToWord# i)) |
| 2025-01-31 13:52:10 +0100 | <dminuoso> | instance Num Word8 where |
| 2025-01-31 13:51:43 +0100 | <dminuoso> | Maybe I need to consult the Haskell Report. |
| 2025-01-31 13:51:29 +0100 | <dminuoso> | c_wraith, tomsmeding: Mmm okay, this is not very satisfying. The actual answer is buried behind CMM implementation details of some primops then. |
| 2025-01-31 13:51:25 +0100 | iamsleepy | (~weechat@2a01:4f9:3070:feff:d8a:11d8:7a8b:29a2) iamsleepy |
| 2025-01-31 13:51:00 +0100 | iamsleepy | (~weechat@2a01:4f9:3070:feff:a9de:dfff:cd7f:fdcd) (Read error: Connection reset by peer) |
| 2025-01-31 13:49:36 +0100 | michals | (~laxmik@wifi-gate-eduroam.fzu.cz) (Client Quit) |
| 2025-01-31 13:48:31 +0100 | laxmik | michals |
| 2025-01-31 13:48:04 +0100 | laxmik | (~laxmik@wifi-gate-eduroam.fzu.cz) laxmik |
| 2025-01-31 13:44:40 +0100 | AlexNoo__ | AlexNoo |
| 2025-01-31 13:40:25 +0100 | monochrom | (trebla@216.138.220.146) |
| 2025-01-31 13:39:27 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
| 2025-01-31 13:36:37 +0100 | monochrom | (trebla@216.138.220.146) (Ping timeout: 248 seconds) |
| 2025-01-31 13:26:09 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |