2024/11/14

Newest at the top

2024-11-14 19:48:11 +0100 <sm> 👍🏻
2024-11-14 19:47:58 +0100 <geekosaur> -S word-splits the parameter
2024-11-14 19:47:49 +0100 <geekosaur> historically the entire shebang line after the interpreter name was passed as a single parameter
2024-11-14 19:47:33 +0100 <geekosaur> the former
2024-11-14 19:47:21 +0100 <sm> I think env requires -S on *bsd (& mac) to allow extra arguments after the executable, GNU/linux doesn't. Or vice versa.
2024-11-14 19:47:11 +0100 <geekosaur> (but some systems that require it don't have it. then again I'm not sure how many people run Illumos)
2024-11-14 19:46:56 +0100 <shapr> The benefit of writing blog posts is that I learn so much!
2024-11-14 19:46:44 +0100housemate(~housemate@146.70.66.228) housemate
2024-11-14 19:46:25 +0100 <shapr> What's env -S ?
2024-11-14 19:45:52 +0100 <sm> ah you showed one. If more arguments are needed, some platforms require env -S
2024-11-14 19:45:23 +0100housemate(~housemate@146.70.66.228) (Max SendQ exceeded)
2024-11-14 19:45:17 +0100 <sm> other issues if scripts are to be shared: how to make a robust shebang line
2024-11-14 19:43:22 +0100smbounces
2024-11-14 19:43:14 +0100housemate(~housemate@146.70.66.228) housemate
2024-11-14 19:42:38 +0100shaprhugs sm
2024-11-14 19:42:34 +0100 <shapr> I like to know all the bits around the edges!
2024-11-14 19:42:28 +0100housemate(~housemate@146.70.66.228) (Max SendQ exceeded)
2024-11-14 19:42:23 +0100 <sm> feel free to ignore me :)
2024-11-14 19:41:53 +0100 <sm> sorry, I'm just giving the most negative (but real) case
2024-11-14 19:41:40 +0100 <sm> (and, getting it working may require either some coding to update it, or installing a few gigabytes of old ghc and deps that may or may not run easily on your machine)
2024-11-14 19:41:37 +0100housemate(~housemate@146.70.66.228) housemate
2024-11-14 19:41:33 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 276 seconds)
2024-11-14 19:40:28 +0100 <shapr> Now that I know, I will mention this!
2024-11-14 19:40:23 +0100 <sm> just because of ghc's evolution and tight/fragile dependencies between haskell packages
2024-11-14 19:40:10 +0100 <shapr> oh, interesting
2024-11-14 19:39:53 +0100 <sm> if you don't pin down ghc (& base) and any other deps your script uses, it's likely to break eventually (or possibly very soon), unlike normal shell scripts
2024-11-14 19:39:42 +0100 <shapr> tell me more?
2024-11-14 19:39:26 +0100housemate(~housemate@146.70.66.228) (Quit: "I saw it in a tiktok video and thought that it was the most smartest answer ever." ~ AnonOps Radio [some time some place] | I AM THE DERIVATIVE I AM GOING TANGENT TO THE CURVE!)
2024-11-14 19:39:17 +0100 <shapr> uh, what is that issue?
2024-11-14 19:39:01 +0100 <sm> Yeah. I hope you'll mention the issue of keeping it running beyond a single ghc release at least. Maybe another post :)
2024-11-14 19:38:56 +0100 <shapr> tempting, but for now I'm gonna cover "how to run a Haskell source file like it's a shell script"
2024-11-14 19:38:41 +0100 <shapr> That makes the subject larger than I can put into a single blog post
2024-11-14 19:37:52 +0100 <sm> https://chrisdone.github.io/hell is the most recent and a particularly interesting one IMHO
2024-11-14 19:37:32 +0100 <sm> there have been lots of attempts to bridge haskell and scripting - https://hackage.haskell.org/packages/search?terms=shell probably includes some of them (sorry)
2024-11-14 19:36:57 +0100 <sm> stack scripts and cabal scripts are important for using deps / reproducibility / sharing, already mentioned by tomsmeding
2024-11-14 19:36:09 +0100 <shapr> oh no, what else am I missing?
2024-11-14 19:35:30 +0100 <sm> shapr: quite a bit, I must tell you :)
2024-11-14 19:32:59 +0100 <shapr> I'll add that as well
2024-11-14 19:30:24 +0100 <tomsmeding> similarly https://docs.haskellstack.org/en/stable/topics/scripts/
2024-11-14 19:29:38 +0100 <shapr> tomsmeding: thank you!
2024-11-14 19:29:19 +0100 <tomsmeding> documentation about the latter here: https://cabal.readthedocs.io/en/stable/cabal-commands.html#cabal-run
2024-11-14 19:29:09 +0100hellwolf(~user@2001:1530:70:545:809e:22e1:baa3:1e4c) (Ping timeout: 246 seconds)
2024-11-14 19:27:58 +0100 <shapr> Am I missing anything?
2024-11-14 19:27:49 +0100 <shapr> and something similar with cabal: https://github.com/shapr/randomtesting/blob/main/Hedgehog.hs#L3
2024-11-14 19:26:37 +0100 <shapr> The only two ways I know are: #!/usr/bin/env runhaskell
2024-11-14 19:26:17 +0100 <shapr> I'm writing a small blog post about using Haskell for "shell scripting", or maybe "how to run a Haskell source file"
2024-11-14 19:25:51 +0100shapr(~user@2601:19c:417e:5434:4627:df70:3bf6:c2cb) shapr
2024-11-14 19:11:58 +0100housemate(~housemate@146.70.66.228) housemate
2024-11-14 19:09:50 +0100alexherbo2(~alexherbo@2a02-8440-3313-668b-a9ec-921f-0511-ee3f.rev.sfr.net) (Remote host closed the connection)
2024-11-14 19:09:33 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)