Vidar Holen

darwin_amd64 is the same as the already available darwin.x86_64.

@sparrc The Homebrew builds are great, but since they're not upstream builds and can't be (re-)produced by the ShellCheck build system, this is not the place for them.

This format appears to be very specific to GitHub and highly over-engineered, so it's not currently in a state where I'd want to support it upstream. This issue can be...

You're certainly right. It's might be a bit tricky to fix though. ShellCheck's handling of `set -e` is naively to look for `set -e` or equivalent anywhere in the script,...

There is some logic in excluding `$#`, but empirically it appears to be pretty rare to check it without then using `$@` or `$1` based on the result. Is this...

`set -e` certainly has [many issues](https://mywiki.wooledge.org/BashFAQ/105). Part of what it does is to forego exiting when a failing command is used as a condition, such as with `if`, `while` and...

`;` lists are fortunately not subject to this, but yes, I think this makes sense. If the `&&` is: * not in a context where exit would already be ignored,...

Do you have guarded shell specific code in this script, e.g. `if [ -n "$BASH_VERSION" ]; then bash-specific-code-here; fi`? If not, just setting the shell to `sh` should be enough....

ShellCheck currently warns about some mid- and end tokens like do/done/fi/esac because it's not at all obvious that the "then" and "fi" are literal in `if true then true fi`...

Can you post `free` output before and after? Make sure chrome/firefox exits completely and isn't running their preloaded single instance processes in the background.