Tiny Nix utility to write nix shell scripts for // languages, like Go or Kotlin (make an issue if you would like more!).
Thanks to Nix magic,
- it allows you to pin the version of the language you want to the script (rather than to the system).
Just have Nix installed.
Just add the following preface to your script:
#! /usr/bin/env nix
#! nix shell github:cottand/hash2slash/v0.1#go-run --quiet --command hash2slash-go-run
package main
import "os"
func main() {
println("Hello world, I am a script!")
}Congrats! You just made a Go script, without Go or Yaegi installed in your system. You can run it as you would a bash script.
#! /usr/bin/env nix
#! nix shell /home/cottand/dev/cottand/hash2slash#kotlin --quiet --command hash2slash-kotlin
fun greet(then: String) = "Hello, $then!"
println(greet("I am a script") + args[1])#! /usr/bin/env nix
#! nix shell github:cottand/hash2slash/v0.1#go-run --quiet --command hash2slash-go-run
package main
import "os"
func main() {
println("Hello world, I am a script!")
}See more at example/!
Yes, mostly. But hash2slash does not take care of that, so you have to look into how your language of choice usually does that for scripts.
-
For Kotlin, it means annotations in a
*.main.ktsfile. -
For Go (with yaegi) it means you have to set
GOPATHand install your libs in there.
You do not need hash2slash to run those - you can just use nix shell.
You can read more here.
Because Go and Kotlin (and even their compiled/interpreted variants, like Yaegi or native Kotlin scripting) do
not handle multi-line shebangs (#!) well, but nix shell requires them.
So what we do here is simply replace them with good old slash comments (//) before running the script.
That is not a question, but yes. It still should not stop you from trying this out 'fearlessly' (as far as compatibility goes), because by pinning the version of hash2slash to your script, updates to this utility will not break your scripts.
#! nix shell github:cottand/hash2slash/v0.1#go-run
this part ^^^^