shh

FWIW there are several Haskell and OCaml shell projects on this wiki page, which is editable: Internal DSLs for Shell - https://github.com/oils-for-unix/oils/wiki/Internal-DSLs-for... and ones in many other languages like Scheme and Lisp e.g. https://github.com/jgoerzen/hsh/wiki https://github.com/luke-clifton/shh/tree/master/shh And also a page of alternative shells: https://github.com/oils-for-unix/oils/wiki/Alternative-Shell...

shh is a really cool package, and so is turtle and shelly: https://hackage.haskell.org/package/turtle/docs/Turtle-Tutor... https://hackage.haskell.org/package/shelly shh's "Alternatives" section summarises nicely some of the differences between these: https://github.com/luke-clifton/shh#alternatives shh has a neat [fmt| ... |] macro that gets you around escaping strings. shh generally has more Template Haskell support; you may or may not like this. I am personally leaning towards shh because of its "native pipe style".

Author here. My main use for this is incremental migration away from bash. I'm not saying this is the best way to do scripts, but it's a pretty great stepping stone. Just following the cargo culting guide [0] can already uplift a bash script without changing the logic too much. From there you can start adding structure. My secondary use case is little scripts in NixOS/nixpkgs. There are some helpers in there that make it quite convenient. [0] https://github.com/luke-clifton/shh/blob/master/docs/porting...

Author of Shh [0] here. I've replaced a lot of Bash with Haskell (it's great!). I wrote Shh to help me out with that. I ended up liking PyF [1] for quasiquoting. A friend of mine worked with the author a while ago to strip down it's dependencies, so it's easy to justify. It's what I recommend in my cargo culting guide [2]. [0] https://hackage.haskell.org/package/shh [1] https://hackage.haskell.org/package/PyF [2] https://github.com/luke-clifton/shh/blob/master/docs/porting...