Newest at the top
| 2025-01-10 02:51:02 +0100 | <euouae> | how can I make this the default behavior? |
| 2025-01-10 02:48:03 +0100 | hawer | (~newyear@2.219.56.221) |
| 2025-01-10 02:47:52 +0100 | _73 | (~user@pool-173-76-100-193.bstnma.fios.verizon.net) _73 |
| 2025-01-10 02:47:12 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2025-01-10 02:45:13 +0100 | <euouae> | nice! thank you!!! |
| 2025-01-10 02:45:00 +0100 | <geekosaur> | it says the latest snapshot for 9.4.8 is 21.25 |
| 2025-01-10 02:44:46 +0100 | <geekosaur> | stackage.org has a list |
| 2025-01-10 02:44:30 +0100 | <euouae> | How do I figure out which snapshot to use with stack if I have ghc 9.4.8? Does it follow that version? |
| 2025-01-10 02:44:08 +0100 | <geekosaur> | although supposedly with the next patch release to 9.6 that will become ghcup recommended |
| 2025-01-10 02:43:58 +0100 | <euouae> | I am new to this stuff (or it's been years) so I don't remember any of it |
| 2025-01-10 02:43:49 +0100 | <euouae> | Yeah that makes sense, more stable |
| 2025-01-10 02:43:39 +0100 | <geekosaur> | also, while stack snapshots tend to be fairly recent, ghcup is quite conservative |
| 2025-01-10 02:43:28 +0100 | <euouae> | I just installed the shim like you said, but I guess that was anothe rthing |
| 2025-01-10 02:42:21 +0100 | <geekosaur> | stack predates ghcup and was intended to be an all-in-one solution |
| 2025-01-10 02:42:19 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-10 02:41:52 +0100 | HappyNewYear2025 | (~newyear@2.219.56.221) (Ping timeout: 244 seconds) |
| 2025-01-10 02:41:19 +0100 | <geekosaur> | (but then you have to build your own HLSs to work with them) |
| 2025-01-10 02:41:01 +0100 | <geekosaur> | if you don't install the ghcup shim it even installs its own private ghcs instead of ghcup's |
| 2025-01-10 02:40:42 +0100 | <geekosaur> | because stack does things its own way |
| 2025-01-10 02:40:33 +0100 | Guest57 | (~Guest57@2a00:fbc:ead6:daa8:3d67:28a5:8699:d1db) |
| 2025-01-10 02:40:28 +0100 | orangeFlu | (~orangeFlu@240-100-179-143.ftth.glasoperator.nl) (Quit: Lost terminal) |
| 2025-01-10 02:40:20 +0100 | <geekosaur> | if you want to change it, use a different resolver |
| 2025-01-10 02:40:18 +0100 | <euouae> | why is LTS 9.8.4 and ghcup recommended is different versions? |
| 2025-01-10 02:40:14 +0100 | otto_s | (~user@p5de2f8cc.dip0.t-ipconnect.de) |
| 2025-01-10 02:40:00 +0100 | <geekosaur> | yes, that5 LTS uses 9.8.4 |
| 2025-01-10 02:39:55 +0100 | <euouae> | from the link I can see resolver: compiler: ghc-9.8.4 |
| 2025-01-10 02:39:36 +0100 | <geekosaur> | uh, there should always be one in there, if there isn't then it should use the one from the global as a default but it should always add one |
| 2025-01-10 02:39:13 +0100 | <euouae> | it says snapshot: url: https://raw.githubusercontent.com/commercialhaskell/stackage-snapshots/master/lts/23/3.yaml |
| 2025-01-10 02:38:47 +0100 | <euouae> | there is none, I created the project with `stack new foo` |
| 2025-01-10 02:38:38 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) Smiles |
| 2025-01-10 02:38:33 +0100 | <geekosaur> | what's the snapshot (or resolver) in your stack.yaml? |
| 2025-01-10 02:38:15 +0100 | otto_s | (~user@p4ff270f4.dip0.t-ipconnect.de) (Ping timeout: 244 seconds) |
| 2025-01-10 02:33:34 +0100 | <euouae> | I think it retunrs the version in ~/.stack/global-projects/stack.yaml as `resolver: nightly-2024-09-26` but how should I configure my setup to prevent this? I can't load lsp correclty |
| 2025-01-10 02:32:51 +0100 | <euouae> | for my project that I craeted with stack 3.1.1? |
| 2025-01-10 02:32:41 +0100 | <euouae> | Hello why does `stack --stack-yaml stack.yaml exec ghc -- --numeric-version` return 9.8.4? |
| 2025-01-10 02:32:08 +0100 | euouae | (~euouae@user/euouae) euouae |
| 2025-01-10 02:31:22 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-10 02:27:22 +0100 | supercode | (~supercode@user/supercode) (Quit: Client closed) |
| 2025-01-10 02:26:56 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-10 02:26:43 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Remote host closed the connection) |
| 2025-01-10 02:18:41 +0100 | takuan | (~takuan@178-116-218-225.access.telenet.be) (Ping timeout: 248 seconds) |
| 2025-01-10 02:18:07 +0100 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2025-01-10 02:15:36 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-10 02:10:55 +0100 | xff0x | (~xff0x@2405:6580:b080:900:fcda:45c6:b5b3:4ead) (Ping timeout: 264 seconds) |
| 2025-01-10 02:08:54 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-10 02:08:28 +0100 | orangeFlu | (~orangeFlu@240-100-179-143.ftth.glasoperator.nl) orangeFlu |
| 2025-01-10 02:06:46 +0100 | orangeFlu | (orangeFlu@gateway/vpn/protonvpn/orangeflu) (Ping timeout: 272 seconds) |
| 2025-01-10 02:04:03 +0100 | stiell | (~stiell@gateway/tor-sasl/stiell) stiell |
| 2025-01-10 02:03:17 +0100 | stiell | (~stiell@gateway/tor-sasl/stiell) (Remote host closed the connection) |
| 2025-01-10 02:01:18 +0100 | sprotte24 | (~sprotte24@p200300d16f253600c5a38787ced491fd.dip0.t-ipconnect.de) (Quit: Leaving) |