powscript
powscript copied to clipboard
transpiler written in bash: painless shellscript, indentbased, coffee for the shell with hipster-sparkles v1 BETA LANDED 🎉🎉🎉🎉 thanks fcard!
See https://stackoverflow.com/a/677212/6750494 tl:dr is that `which` is expensive and can change behaviors depending on OS, while `command -v` is a builtin and POSIX.
While implementing this: ```bash array:shift(A) expand ~A=(${~A[@]:slice 1}) ``` I learned that the array initializer expression is parsed like the start of a function. booo! Technically this is a valid...
```sh pow[000] --> x=1 bash: line 37: 1=x: command not found ``` How unfortunate! It spits a bunch of errors for a variety of commands. I am not sure it's...
``` Foo(){ shift; pop; # does not work grr } Foo removeme abc removeme
In order to enable coloring in the readme and the "which languages are used in this project bar" in Github, as well to be considered an own language, Github offers...
@fcard I've modified the README.md example to get it to work again. It almost works again, except for printing the version-property of a parsed json-object. What were your initial ideas...
So from what i've understood is that the compiler is using eval, to stay flexible concerning bash vs sh output. So powscript generally produces this type of output: ``` set?()...
url: http://powscript [dot] isvery [dot] ninja Lets not spread this url yet (work in progress). It actually loads files from `/doc` remotely, so this repo is basically the 'CMS' :)