jnunemaker

function __git_dirty {
  git diff --quiet HEAD &>/dev/null 
  [ $? == 1 ] && echo "!"
}

function __git_branch {
  __git_ps1 "(%s)"
}

function __my_rvm_ruby_version {

gasman

#!/usr/bin/env ruby

# Command line util for acquiring a one-off Twitter OAuth access token
# Based on http://blog.beefyapps.com/2010/01/simple-ruby-oauth-with-twitter/

require 'rubygems'
require 'oauth'

puts <<EOS
Set up your application at https://twitter.com/apps/ (as a 'Client' app),

nutrun

# Do something like: puts "ROCK".blink.bright.cyan

class String
  def red
    "\e[31m#{self}\e[0m"
  end

  def blue
    "\e[34m#{self}\e[0m"
  end  

tpope

set keymap vi-insert
Control-a: beginning-of-line
Control-b: backward-char
Control-d: delete-char
Control-e: end-of-line
Control-f: forward-char
Control-k: kill-line
Control-n: next-history
Control-p: previous-history
set keymap emacs-ctlx

alkesh

#!/usr/bin/env ruby

require 'rubygems'
require 'curb'
require 'uri'

#uri = URI.parse("https://oa.bt.com/ews/Services.wsdl")

c = Curl::Easy.new("https://oa.bt.com/ews/Exchange.asmx")
#c = Curl::Easy.new("https://oa.bt.com/ews/Services.wsdl")

coreyhaines

--colour
-I app

erikh

#!/usr/bin/env sh

##
# This is script with usefull tips taken from:
#   https://github.com/mathiasbynens/dotfiles/blob/master/.osx
#
# install it:
#   curl -sL https://raw.github.com/gist/2108403/hack.sh | sh
#

javan

//
// Example usage: phantomjs screenshot.js http://yahoo.com /tmp/yahoo.png
//

var system = require('system');
var url = system.args[1];
var filename = system.args[2];
var page = new WebPage();

page.open(url, function (status) {

mattwynne

class Organization
  def to_param
    "42"
  end
  def saved?
    rand > 0.5
  end
end

jcoglan

The OAuth 2.0 Authorization Framework

This document is intended to be a simplified version of the OAuth 2.0 specification. In particular it has been written with implementors in mind, and as such attempts to trim the spec down to just what you need to implement an OAuth provider or client. It is necessarily not complete, but attempts to introduce spec requirements in the same order in which the protocol proceeds in practise, with everything you need to know about each protocol endpoint brought together in one place rather than scattered across a large document.