See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
| #!/bin/bash | |
| ############################ | |
| #script function | |
| ############################ | |
| setProperty(){ | |
| awk -v pat="^$1=" -v value="$1=$2" '{ if ($0 ~ pat) print value; else print $0; }' $3 > $3.tmp | |
| mv $3.tmp $3 | |
| } | |
| ############################ |
| # Python virtual env alias | |
| alias activate='test -d ENV && source ./ENV/bin/activate || echo "No Virtualenv in the current folder"' | |
| alias mkenv='test -d ENV && echo "Already exists" || virtualenv --system-site-packages ENV; activate' |