Newest at the top
| 2024-12-28 13:35:24 +0100 | <Leary> | Re the former option, it really shouldn't be something that disturbs your flow or substantially slows you down; I suspect you need a better (or better configured) WM. |
| 2024-12-28 13:34:33 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds) |
| 2024-12-28 13:33:46 +0100 | <Leary> | You can either manually edit the haskell file, or write your automation there. E.g. an IO action that pull the most recently modified .hvml file from a test directory and runs it. |
| 2024-12-28 13:30:52 +0100 | <SrPx> | unless you mean I should create a script to edit a comment in a Haskell file on HVM3 whenever I want to run an hvml file on VIM, which sounds hacky as hell |
| 2024-12-28 13:30:17 +0100 | <SrPx> | Leary: how can I do that if the commands aren't static? for example if I want to run a file X.hvml, I'd do 'hvml run X.hvml'. that's not a static command I want to run every time I save a file |
| 2024-12-28 13:30:11 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 13:29:50 +0100 | annamalai | (~yaaic@2409:4072:609c:96c7::1350:d8b1) annamalai |
| 2024-12-28 13:26:17 +0100 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2024-12-28 13:17:34 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-12-28 13:16:33 +0100 | <Leary> | SrPx: Put the commands you want to run in `-- $> ...` comments in the haskell files, and pass ghcid/ghciwatch the appropriate flag to tell it to look for and run these comments. |
| 2024-12-28 13:13:37 +0100 | CiaoSen | (~Jura@2a05:5800:2ca:8300:ca4b:d6ff:fec1:99da) (Ping timeout: 248 seconds) |
| 2024-12-28 13:13:22 +0100 | <SrPx> | the 3 part is the issue, ghcid for example doesn't allow that |
| 2024-12-28 13:13:14 +0100 | <SrPx> | again what I need seems to be: 1. leave a ghci session open in the background; 2. have it reload whenever a file changes; 3. allow me to, from a separate terminal, run haskell commands on it |
| 2024-12-28 13:13:05 +0100 | <SrPx> | work* |
| 2024-12-28 13:13:03 +0100 | <SrPx> | hm that didnt working |
| 2024-12-28 13:12:54 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 13:06:16 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-12-28 13:03:28 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) (Ping timeout: 265 seconds) |
| 2024-12-28 13:02:17 +0100 | caconym | (~caconym@user/caconym) caconym |
| 2024-12-28 13:00:04 +0100 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2024-12-28 12:59:39 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 12:55:00 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2024-12-28 12:54:46 +0100 | <SrPx> | is it possible to reload ghci with an actual function, not ':r'? i'm trying to call it from an IO block |
| 2024-12-28 12:52:41 +0100 | acidjnk_new3 | (~acidjnk@p200300d6e7283f42bc4ebb891d7561a4.dip0.t-ipconnect.de) acidjnk |
| 2024-12-28 12:50:36 +0100 | euleritian | (~euleritia@dynamic-176-007-157-163.176.7.pool.telefonica.de) (Ping timeout: 252 seconds) |
| 2024-12-28 12:50:09 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds) |
| 2024-12-28 12:49:45 +0100 | tv | (~tv@user/tv) tv |
| 2024-12-28 12:48:07 +0100 | <Leary> | SrPx: You don't need to run anything; it runs automatically when you save changes to the files. |
| 2024-12-28 12:45:26 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 12:42:47 +0100 | <SrPx> | basically just open the repl and watch a named pipe for a lightweight communication between my VIM and it |
| 2024-12-28 12:41:59 +0100 | <SrPx> | oh never mind sonnet provided an easy / obvious solution |
| 2024-12-28 12:40:40 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) lxsameer |
| 2024-12-28 12:39:09 +0100 | <SrPx> | __monty__: every time I make a change it takes that amount of time. yet `:r` on the repl is instant. so ideally all I need is a way to talk to the repl (from another terminal) quickly. almost considering spawning a socket but there must be a built in way |
| 2024-12-28 12:37:51 +0100 | tnt2 | tnt1 |
| 2024-12-28 12:37:51 +0100 | tnt1 | (~Thunderbi@user/tnt1) (Ping timeout: 265 seconds) |
| 2024-12-28 12:37:05 +0100 | tnt2 | (~Thunderbi@user/tnt1) tnt1 |
| 2024-12-28 12:36:48 +0100 | <__monty__> | SrPx: Is it too slow just the first time or every time? I don't think you can speed up `cabal run` much but maybe watching the files with something like ghcid or entr and running `cabal build` whenever the project changes will avoid having to pay the full price of compilation the moment you run code from your editor? |
| 2024-12-28 12:36:00 +0100 | acidjnk_new3 | (~acidjnk@p200300d6e7283f42bc4ebb891d7561a4.dip0.t-ipconnect.de) (Ping timeout: 260 seconds) |
| 2024-12-28 12:32:34 +0100 | <SrPx> | yes but it is still a repl, not sure how that helps with running it from a separate terminal? |
| 2024-12-28 12:32:28 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-12-28 12:31:56 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz) |
| 2024-12-28 12:31:20 +0100 | ljdarj1 | ljdarj |
| 2024-12-28 12:31:20 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds) |
| 2024-12-28 12:31:08 +0100 | ljdarj1 | (~Thunderbi@user/ljdarj) ljdarj |
| 2024-12-28 12:29:34 +0100 | <Leary> | It watches your source and test files for changes and reloads a repl in the background. |
| 2024-12-28 12:28:58 +0100 | <SrPx> | that would be ideal |
| 2024-12-28 12:28:54 +0100 | <SrPx> | Leary: I've seen ghciwatch but it seemed unrelated, so you mean it can keep a repl open, and then allow me to access it in a separate terminal? |
| 2024-12-28 12:28:18 +0100 | <mauke> | (IIRC there is no 'optimization' setting in *.cabal files; you'd have to do soemthing like 'ghc-options: -O2') |
| 2024-12-28 12:28:12 +0100 | <Leary> | SrPx: When I say repl, I really mean indirectly via ghcid/ghciwatch, as I recommended earlier. They can run `-- $> <code>` comments embedded in haskell files and be made to watch e.g. your .hvml test file for changes. |
| 2024-12-28 12:28:04 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |