scripting-field-guide VS Batsh

I couldn't find a way to have more than one callback per signal, and created a system to have an array of callbacks:

https://github.com/kidd/scripting-field-guide/blob/master/bo...

A nice bonus is that it also keeps the return value of the last non-callback function, so your script behaves better when called from other scripts.

https://github.com/batsh-dev-team/Batsh

https://github.com/tdenniston/bish

(Just fyi. I've been collecting links to similar things because of Reasons).

I wish there was a nicer shell scripting language that simply transpiled to Bash and would generate all this boilerplate code for me. There is https://batsh.org/ which has a nice syntax but it doesn't even support pipes or redirection, making it pretty worthless for shell scripting. I haven't found any other such scripting languages.

There are some languages that compile into bash like Batch. Shell commands can also be called from Python code using this (never tried it): https://plumbum.readthedocs.io/en/latest/index.html

Maybe https://github.com/batsh-dev-team/Batsh

Not really what you're asking for, but a language that compiles to bash for portability reminded me of Batsh [0], a C-like language that compiles to bash for Linux/Mac and batch for Windows.

[0] https://github.com/batsh-dev-team/Batsh

There used to be something called Batsh as well but no longer seems to be actively developed

There are a couple projects that provide a language that compiles to Bash, which gets around Oil's portability problem somewhat. Bish and Batsh come to mind.