quickshiftin

# Short of learning how to actually configure OSX, here's a hacky way to use
# GNU manpages for programs that are GNU ones, and fallback to OSX manpages otherwise
alias man='_() { echo $1; man -M $(brew --prefix)/opt/coreutils/libexec/gnuman $1 1>/dev/null 2>&1;  if [ "$?" -eq 0 ]; then man -M $(brew --prefix)/opt/coreutils/libexec/gnuman $1; else man $1; fi }; _'

mageekguy

<?php

namespace classception;

class asserter
{
	protected $actual = null;

	public function __construct($actual)
	{

mageekguy

	public function acceptClient($clientsSocket)
	{
		$this->pollSocket($clientsSocket)->onRead(array($this, __FUNCTION__));

		$clientSocket = new server\socket($this->acceptSocket($clientsSocket), $this);

		$timeoutHandler = function() use ($clientSocket) {
				$this->writeInfo('Client ' . $clientSocket->getPeer() . ' timeout!');

				$clientSocket->close();

scalp42

resource_not_found = {}
begin
  resources('ruby_block[my-resource-supposed-to-exist]')
rescue Chef::Exceptions::ResourceNotFound
  resource_not_found['ruby_block[my-resource-supposed-to-exist]'] = true
end

template '/etc/my/template.conf' do
  source 'template.conf.erb'
  mode '640'

marmotz

/**
 * VERY simple benchmarker for code.
 * Produce a light report on console.
 *
 * USAGE:
 *
 * Bencher.get('a bench description').start();
 *
 * // code here
 *

mageekguy

# Indenting and Whitespace

Use only tabs, with no space. 
Lines should have no trailing whitespace at the end. 
Files should be formatted with \n as the line ending (Unix line endings), not \r\n (Windows line endings). 
PHP files should be in UTF-8. 
PHP files should begin with `<?php ` and should not have a end tag (no `?>`).
The reasons for this can be summarized as:
* Removing it eliminates the possibility for unwanted whitespace at the end of files which can cause "header already sent" errors, XHTML/XML validation issues, and other problems.
* The closing delimiter at the end of a file is optional.

cvan

// Load an image in your browser and paste this in your console

var i=new Image();i.src=document.location.href;i.onload=function(){var c=document.createElement('canvas');c.width=this.width;c.height=this.height;c.getContext('2d').drawImage(this,0,0);window.location=c.toDataURL('image/png');};

ariesjia

To target IE 6 and 7
@media screen\9 {
    body { background: red; }
} 


To target IE 6, 7 and 8
@media \0screen\,screen\9 {
    body { background: green; }
} 

pvh

The PHP language owner is responsible for the success of Heroku developers building in PHP. They are part of the broader “languages team”, a group of developers with similar language-specific responsibilities and shared infrastructure.

A language owner will be responsible for varying degrees of

• building core language-specific features such as the “build pack”,
• working within the community to improve projects upstream to provide a better experience for Heroku users,
• customer outreach,
• customer support,
• sales support,
• language-specific documentation and content, and
• marketing responsibilities such as attending and speaking at conferences.

lyrixx

#!/bin/bash

# Put this file at: .git/hooks/post-checkout
# and make it executable
# You can install it system wide too, see http://stackoverflow.com/a/2293578/685587

PREV_COMMIT=$1
POST_COMMIT=$2

NOCOLOR='\e[0m'