workshop

I honestly don't know! What I know is that there is an intersection of features that work with polyfills and tweaks in all shells. That intersection has a lot of the spec, but also has a lot that is not specified anywhere. I started to build something here 12 years ago: https://github.com/Mosai/workshop. Then here 2 years ago: https://github.com/alganet/coral Now I'm attacking it from another angle, trying to document what I learned methodically and share the tools I made for me with everyone else.

https://github.com/shellfire-dev https://github.com/shellspec https://oils.pub/ There's probably more. The shell has a ____wide____ userbase with many kinds of users. Depending on your goal, the rabbit hole can go very deep (how portable across interpreters, how dependant on other binaries, how early can it work in a bootstrap scenario, etc). These are mine: https://github.com/alganet/coral https://github.com/alganet/shell-versions https://github.com/Mosai/workshop

I did a similar thingy a while back: https://github.com/alganet/coral/blob/master/doc/spec/requir... It also does references (`require `something from inside modules) and some stuff. It is missing the download component though. I've also worked on https://github.com/Mosai/workshop, a previous attempt at shell tooling (please do not use it!) Also, there was a popular https://github.com/pixelomer/bashpm at some point. Most stable thing would probably be: https://github.com/shellfire-dev Here are my thoughts working in this "hobby" for the last 6 years: - External tools are bad for shell portability and performance. It costs more to invoke "cut" than to do a loop and a couple of parameter expansions. Tools like cut, sed and similar are not suited for small strings, they are for large files. - ksh93 and ksh2020 support is possible, see: https

It's funny you mentioned the exact problems I'm trying to solve. For the tests, I'm writing my own xUnit tool [1]. It doesn't use any fancy stuff, runs on set -euf, it's tested by itself and works on every POSIX-like shell that I could find (bash, dash, zsh, (m|pd)ksh, yash, posh, even busybox) and many different versions and OSs. On the functional side, I've decided that I need to test using virtual machines. The test matrix tool that can spawn and test on them is almost ready [2], it already tests the library itself and exports the matrix configuration to Travis. Very early stuff though and doesn't even touch problems like partition routines you mentioned, but overall I'm happy with the results, considering everything runs under 70Kb of code. [1] https://github.com/Mosai/workshop/blob/master/doc/posit.md [2] https://github.com/Mosai/wor