Scott McMillin scottymac

## my git shell prompt with dirty status
function parse_git_dirty {
  git diff --quiet || echo "•"
}

function parse_git_branch {
  ref=$(git symbolic-ref HEAD 2> /dev/null) || return
  echo "["${ref#refs/heads/}"$(parse_git_dirty)]"
}

YELLOW="\[\033[0;33m\]"

## gist:32347
from http://radar.oreilly.com/2008/11/why-i-like-twitter.html

"There's a real lesson to Facebook here about giving other services (like Twitter) access to their social graph. They have the best one going, but because they try to keep users coming back to their interface, and even the applications built on their service have to live in Facebook, they end up as a ghetto rather than a true internet service. It's the data, not the interface! Let other people use your data, build on it, and it will still belong to you. Hold it too tight, and they will compete with it."


## gist:307
test 1

Forking trevor's gist
	function parse_git_dirty {
	git diff --quiet \|\| echo "•"
	}

	function parse_git_branch {
	ref=$(git symbolic-ref HEAD 2> /dev/null) \|\| return
	echo "["${ref#refs/heads/}"$(parse_git_dirty)]"
	}

	YELLOW="\[\033[0;33m\]"
	from http://radar.oreilly.com/2008/11/why-i-like-twitter.html

	"There's a real lesson to Facebook here about giving other services (like Twitter) access to their social graph. They have the best one going, but because they try to keep users coming back to their interface, and even the applications built on their service have to live in Facebook, they end up as a ghetto rather than a true internet service. It's the data, not the interface! Let other people use your data, build on it, and it will still belong to you. Hold it too tight, and they will compete with it."