dannyben

5 ms·

1. 1.▲
   by dannyben 5y ago

   Ok. Here: https://bashly.dannyb.co/usage/getting-started/
2. 2.▲
   by dannyben 5y ago

   You can see the autohotkey script in the same folder: https://github.com/DannyBen/bashly/blob/master/demo/demo-mak... It was created with asciinema and svg-term-cli
3. 3.▲
   by dannyben 5y ago

   Heh. Yeah, this would be a satisfying nerdy accomplishment. Note there is a docker image if you want to use it without having Ruby.
4. 4.▲
   by dannyben 5y ago

   No need to repeat step 3. Code for each command (in case you want a bash script with subcommands), is placed in `src/<command_name>_command.sh`. Running `bashly generate` will always read it and re-merge it. I think this is a goo
5. 5.▲
   by dannyben 5y ago

   I created bashly to support a simple use case: When you want to create a bash script - and you choose bash for portability or for whatever reason - and still want to have a decent-looking command line interface, without investing effort in
6. 6.▲
   by dannyben 5y ago

   No. No DSL. 1. Define your commands + flags + args in YAML (`bashly init` creates this YAML). 2. Bashly generates the standalone script and empty "placeholder" scripts for your actual bash code (`bashly generate`). 3. You plug in
7. 7.▲
   by dannyben 5y ago

   Well - there is a documentation site if you want to stare... the animated gif is for people who want a "drive-by" look at what it does.