bashstyle
bashstyle copied to clipboard
progrium
Let's do Bash right!
Added info to avoid have errors making comparisons with quoted variables using numbers.
How about standardizing on braces? ``` bash # Yep echo "${var}" echo "$1" # Nope echo "$var" ```
I using tabs, because of the great application in these heredocs: ``` bash #!/usr/bin/env bash main() { cat > "message.txt"
I tried to make this as uncontentious as possible, with `set -uo pipefail` being the "do this 100% of the time by default" advice and `set -e` being the "but...
set -u
I would add `set -u` into your advice for `set -eo pipefail`, i.e. `set -euo pipefail` An enhancement to that is to fail early in a script with useful feedback....
Please take a look at LCOV.SH full BASH implementation of coverage… no need for additional interpreters like RUBY or BINARY executable in your machine. Check coverage of BASH just with...
This link: http://www.kfirlavi.com/blog/2012/11/14/defensive-bash-programming/ is now broken. Not sure where I would look to PR a replacement :/
> Use .sh or .bash extension if file is meant to be included/sourced. Never on executable script. I'm curious about the philosophy of NOT including .sh as a suffix for...
