dblock

# inspired by https://github.com/rspec/rspec-core/pull/596
require 'rspec/core/formatters/base_formatter'

module RSpec
  module Core
    module Formatters
      class FailuresFormatter < BaseFormatter
        
        def dump_failures
          return if failed_examples.empty?

firedfox

const PHANTOM_FUNCTION_PREFIX = '/* PHANTOM_FUNCTION */';

var page = require('webpage').create();

page.onConsoleMessage = function(msg) {
    if (msg.indexOf(PHANTOM_FUNCTION_PREFIX) === 0) {
        eval('(' + msg + ')()');
    } else {
        console.log(msg);
    }

fnichol

A Common .ruby-version File For Ruby Projects

Background

I've been using this technique in most of my Ruby projects lately where Ruby versions are required:

• Create .rbenv-version containing the target Ruby using a definition name defined in ruby-build (example below). These strings are a proper subset of RVM Ruby string names so far...
• Create .rvmrc (with rvm --create --rvmrc "1.9.3@myapp") and edit the environment_id= line to fetch the Ruby version from .rbenv-version (example below).

Today I learned about another Ruby manager, rbfu, where the author is using a similar technique with .rbfu-version.

fhwang

namespace :spec do
  namespace :units do
    desc "Run unit specs with PATTERN in the spec file name"
    RSpec::Core::RakeTask.new(:selective => "db:test:prepare") do |t|
      t.pattern = FileList["spec/**/*#{ENV['PATTERN']}*_spec.rb"].exclude("spec/integration/**/*_spec.rb")
    end
  end

  namespace :integration do
    desc "Run integration specs with PATTERN in the spec file name"

sgmurphy

<?php
/**
 * Scrape the number of podcast reviews from iTunes for all country specific storefronts.
 *
 * @author Sean Murphy <sean@iamseanmurphy.com>
 */

$podcast_id = '366931951';	// Startups For the Rest of Us
//$podcast_id = '318567721';	// techzing

jacobbubu

mr	Marathi
bs	Bosnian
ee_TG	Ewe (Togo)
ms	Malay
kam_KE	Kamba (Kenya)
mt	Maltese
ha	Hausa
es_HN	Spanish (Honduras)
ml_IN	Malayalam (India)
ro_MD	Romanian (Moldova)

oodavid

Deploy your site with git

This gist assumes:

• you have a local git repo
• with an online remote repository (github / bitbucket etc)
• and a cloud server (Rackspace cloud / Amazon EC2 etc)
  • your (PHP) scripts are served from /var/www/html/
  • your webpages are executed by apache
• apache's home directory is /var/www/

saetia

OS X Preferences

---

most of these require logout/restart to take effect

# Enable character repeat on keydown
defaults write -g ApplePressAndHoldEnabled -bool false

# Set a shorter Delay until key repeat

artero

Launch Sublime Text 2 from the Mac OS X Terminal

Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.

open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl

You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html

Installation

bergie

config.json
reading-image.png