Izaak "Zaak" Beekman

Some potentially helpful links: - https://github.com/vorpaljs/bash-parser - https://github.com/idank/bashlex - https://github.com/grncdr/js-shell-parse - http://hackage.haskell.org/package/language-sh - https://google.github.io/styleguide/shell.xml - https://github.com/bahamas10/bash-style-guide - http://wiki.bash-hackers.org/scripting/style - https://github.com/skudriashev/bashlint

@kenden we [already use shellcheck](https://github.com/kvz/bash3boilerplate/blob/0289532f187c6ebcac9dbc3b1be23fb54e1d683c/test/acceptance.sh#L230-L251). This is about style beyond linting/syntax checking 😉

I use it, but there are some problems... mostly having to do with arithmetic expressions, and the inability to run `shfmt` if you need to dereference counter variables in arithmetic...

@mvdan Thanks for chiming in! I'll have to test again with the latest version. If anything still seems broken I'll file a bug report. Also, yes, I know I should...

TL;DR; Perhaps not AS elegant as a config file, but since you can specify defaults in usage string, you can add some logic [here](https://github.com/kvz/bash3boilerplate/blob/master/main.sh#L137-L146)---that instead of using a here-doc---just reads...

In your ideal world, how would you want to specify the defaults for your use case? On Thu, Jul 6, 2017 at 11:18 PM QwertyZW wrote: > @kvz that's for...

@QwertyZW I think I'm following you so far... the intent of my last question, is: "In an ideal world, how would you want to specify/control the defaults on each environment?...

I'm thinking of changing things so that long options are the default/required and short options are optional... in the mean time, you'll have to do something like -w --walltime-template, -W...

no... working on backtrace first... not sure if I'll get to this anytime soon

Yes, I think Open coarrays build script passed arguments to other scripts, only some of which are actually consumed. Been meaning to add an opt-in check for invalid flags.