Newest at the top
| 2025-05-04 22:13:03 +0200 | Arpad | (~Arpad@2a02:ab88:38d:4700::b0d5) (Quit: Client closed) |
| 2025-05-04 22:11:20 +0200 | <hellwolf> | thanks everyone. learned a new trick today. |
| 2025-05-04 22:11:05 +0200 | <hellwolf> | probably not worth the effort, but good to know. |
| 2025-05-04 22:10:56 +0200 | <hellwolf> | that's added by the linking when building the binary |
| 2025-05-04 22:10:46 +0200 | <hellwolf> | 3 ± 2 seconds difference |
| 2025-05-04 22:10:16 +0200 | chexum | (~quassel@gateway/tor-sasl/chexum) chexum |
| 2025-05-04 22:07:15 +0200 | <hellwolf> | cabal "$@" -v1 repl --repl-options="-e main" RunYol |
| 2025-05-04 22:07:11 +0200 | <hellwolf> | to: |
| 2025-05-04 22:07:09 +0200 | <hellwolf> | "$runbin" || die |
| 2025-05-04 22:07:09 +0200 | <hellwolf> | runbin=$(cabal "$@" -v0 list-bin runyol) |
| 2025-05-04 22:07:09 +0200 | <hellwolf> | from |
| 2025-05-04 22:05:45 +0200 | <int-e> | err, --ghc-arg= |
| 2025-05-04 22:05:33 +0200 | <hellwolf> | let me see if it's faster |
| 2025-05-04 22:05:18 +0200 | <hellwolf> | hurray |
| 2025-05-04 22:05:12 +0200 | <hellwolf> | it worked |
| 2025-05-04 22:05:11 +0200 | <int-e> | does `cabal run` even work for the thing you're testing |
| 2025-05-04 22:05:01 +0200 | <int-e> | runghc will probably need something like runghc -ghc-arg=-i -ghc-arg=exe Main.hs |
| 2025-05-04 22:03:51 +0200 | <hellwolf> | | Internal error when trying to open a repl for the package fake-package-0. The package is not in the set of available targets for the project plan, which would suggest an inconsistency between readTargetSelectors and resolveTargets. |
| 2025-05-04 22:01:20 +0200 | <int-e> | maybe: cabal -v0 repl --repl-options="-e main" |
| 2025-05-04 21:58:10 +0200 | <hellwolf> | didn't work |
| 2025-05-04 21:58:08 +0200 | <hellwolf> | cabal exec runghc runyol |
| 2025-05-04 21:56:58 +0200 | <geekosaur> | cabal exec runghc … ? |
| 2025-05-04 21:56:48 +0200 | <hellwolf> | anyways, feeling like beating a dead horse now, I guess I will have to live with it or do something about it either using stack just for this or fix cabal. |
| 2025-05-04 21:55:45 +0200 | <hellwolf> | *I just want to |
| 2025-05-04 21:55:36 +0200 | <hellwolf> | now that I have that cabal project file, I just run that within a interpretation mode. |
| 2025-05-04 21:55:20 +0200 | Square | (~Square@user/square) Square |
| 2025-05-04 21:54:48 +0200 | <hellwolf> | I create cabal project file and run cabal <-- what I do |
| 2025-05-04 21:54:32 +0200 | <hellwolf> | EOF |
| 2025-05-04 21:54:31 +0200 | <hellwolf> | runyol.cabal |
| 2025-05-04 21:54:31 +0200 | <hellwolf> | $cabal_path |
| 2025-05-04 21:54:31 +0200 | <hellwolf> | packages: |
| 2025-05-04 21:54:31 +0200 | <hellwolf> | package-dbs: clear, global, ${cabal_package_db}, ${yolc_package_db} |
| 2025-05-04 21:54:31 +0200 | <hellwolf> | cat <<EOF |
| 2025-05-04 21:53:32 +0200 | <haskellbridge> | <sm> plus, I think relying on hidden package environment files will suck |
| 2025-05-04 21:52:57 +0200 | <haskellbridge> | <sm> though, that's a pain because it varies between linux / mac / freebsd, whether env -S is required in the shebang line |
| 2025-05-04 21:52:04 +0200 | <haskellbridge> | <sm> well a runghc shebang script could pass ghc opts to runghc |
| 2025-05-04 21:51:43 +0200 | <haskellbridge> | <sm> but if you want people to write scripts using your lib easily.. then no |
| 2025-05-04 21:51:40 +0200 | <hellwolf> | cabal, or stack has, I know of. |
| 2025-05-04 21:51:35 +0200 | <hellwolf> | runghc has script header too? |
| 2025-05-04 21:51:28 +0200 | <hellwolf> | that's right |
| 2025-05-04 21:51:15 +0200 | <haskellbridge> | <sm> though you could specify them in the script header too I expect |
| 2025-05-04 21:51:06 +0200 | <hellwolf> | though, I do have a few to list beyond GHC2024 :D |
| 2025-05-04 21:50:37 +0200 | <hellwolf> | I learned that now. |
| 2025-05-04 21:50:30 +0200 | <haskellbridge> | <sm> more verbosity.. but more robust |
| 2025-05-04 21:50:30 +0200 | rvalue- | rvalue |
| 2025-05-04 21:50:07 +0200 | <haskellbridge> | <sm> that's why a lot of people write them in the modules |
| 2025-05-04 21:49:27 +0200 | <hellwolf> | gosh, side effect of relying on build system to list default extensions. |
| 2025-05-04 21:49:11 +0200 | <hellwolf> | I tried runghc: it has one other problem, I listed some defaultr extensions in cabal file :D |
| 2025-05-04 21:49:02 +0200 | acidjnk_new3 | (~acidjnk@p200300d6e71c4f52d4f1201e65d300bb.dip0.t-ipconnect.de) acidjnk |
| 2025-05-04 21:48:40 +0200 | acidjnk_new3 | (~acidjnk@p200300d6e71c4f524d98fe298d45bbdf.dip0.t-ipconnect.de) (Remote host closed the connection) |