bash

GitHub - azet/community_bash_style_guide: Community Bash Style Guide: writing useful and modern bash scripts, seriously. When to use bash and when to avoid bash it’s rather simple: does it need to glue userland utilities together? use bash. does it need to do complex tasks (e.g. database queries)? use something else. Why? … It consumes a lot of time and is often very difficult to debug in comparison to dynamic programming languages such as python, ruby or even perl....

Small information nuggets and recipies about Unix

My template for when I need to do bash scripts with both a “human” and a “machine” interface: Template for interactive bash scripts: supports command line options with values prompts for any missing parameters/arguments https://gist.github.com/hugocf/8147608 Update 2016-06-02: Moved to repo @hugocf/scripts