3 ms·

And test them on a shell that isn't bash. Even with the --posix option bash accepts non-standard bashisms, particularly the execrable 'extension' of '>&'.

• bryanlarsen 11y ago
  That's why I always put "#!/usr/bin/env bash" at the top of my scripts. Most were written to be portable, but unless it's been well tested, it's best to consider it not portable. Fail early and predictably rather than in strange ways.
  • stephenr 11y ago
    That.. Isn't the solution. The point is that bash is not a good target for shell scripts, not that you should use env to detect the location of bash.
    • nailer 11y ago
      If you only use *nix platforms the default to bash, why not write bash scripts?