Alexander Merkulov merqlove

I highly suspect that the RSpec core team all use black backgrounds in their terminals because sometimes the colors aren’t so nice on my white terminal

I certainly use a black background. I'm not sure about the other RSpec core folks. Regardless, if there are some color changes we can make that would make output look good on a larger variety of backgrounds, we'll certainly consider that (do you have some suggested changes?). In the meantime, the colors are configurable, so you can change the colors to fit your preferences on your machine. First, create a file at

ruby-1.9.3 cumulative performance patch for rbenv

(I guarantee nothing. No warranty I am not responsible blah blah blah. Seems to work great for me so far. Thanks to Tyler Bird and Slayer who I forked this from.)

From merqlove:

I just made little improvement to this fix:

Now you can select Ruby BUILD via same name variable. Otherwise build version will be used by default.

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title>Autocomplete Search With Semantic UI</title>
	<link rel="stylesheet" href="semantic/dist/semantic.css">
	</head>
	<body>

	AllCops:
	RunRailsCops: true

	# Commonly used screens these days easily fit more than 80 characters.
	Metrics/LineLength:
	Max: 120

	# Too short methods lead to extraction of single-use methods, which can make
	# the code easier to read (by naming things), but can also clutter the class
	Metrics/MethodLength:

	# Postgresql fancy datatypes!

	* array
	* hstore (=~ hash)
	* json
	* jsonb


	Philippe Creux - [@pcreux](http://twitter.com/pcreux)

	# Generates necessary certificates to ~/.docker
	#
	# Usage:
	# bundle install
	# ruby certgen.rb <domain>

	require 'certificate_authority'
	require 'fileutils'

	if ARGV.empty?

	describe('e2e: main', function() {

	var ptor;

	beforeEach(function() {
	browser.get('/');
	ptor = protractor.getInstance();
	});

	it('should load the home page', function() {

	# This is an example of metaprogramming in the Elixir language.
	#
	# We will define a domain specific language (DSL) for the definition
	# of a service which is watched by several sensors.
	# Each sensor watches some property/functionality of the service and
	# returns the result of the check.
	#
	# To determine if the service is functioning properly, we need functions
	# to run all the sensors' code and gather the returned data.
	#

	var CrossfadeSample = {playing:false};

	CrossfadeSample.play = function() {
	// Create two sources.
	this.ctl1 = createSource(BUFFERS.drums);
	this.ctl2 = createSource(BUFFERS.organ);
	// Mute the second source.
	this.ctl1.gainNode.gain.value = 0;
	// Start playback in a loop
	if (!this.ctl1.source.start) {

	#! /bin/sh


	### BEGIN INIT INFO
	# Provides: pumacontrol
	# Required-Start: $remote_fs $syslog
	# Required-Stop: $remote_fs $syslog
	# Default-Start: 2 3 4 5
	# Default-Stop: 0 1 6
	# Short-Description: Puma web server