vheon

set cot=menu,menuone

ino <BS> <BS><C-r>=getline('.')[col('.')-3:col('.')-2]=~#'\k\k'?!pumvisible()?"\<lt>C-n>\<lt>C-p>":'':pumvisible()?"\<lt>C-y>":''<CR>
inoremap <expr> <CR>    pumvisible() ? "\<C-y>" : ""
inoremap <expr> <Tab>   pumvisible() ? "\<C-n>" : "\<Tab>"
inoremap <expr> <S-Tab> pumvisible() ? "\<C-p>" : "\<S-Tab>"

function! s:skinny_insert(char)
  if !pumvisible() && !exists('s:skinny_complete') &&
              \ getline('.')[col('.') - 2].a:char =~# '\k\k'

jdewit

var assert = require('chai').assert,
    path = require('path'),
    browserName = process.env.browser || 'chrome',
    protractor = require('protractor'),
    webdriver = require('selenium-webdriver'),
    exec = require('child_process').exec,
    util = require('util')
;

var driver = new webdriver.Builder().usingServer('http://localhost:4444/wd/hub').withCapabilities(webdriver.Capabilities[browserName]()).build();

cjonstrup

<?php
use Illuminate\Console\Command;
use Illuminate\Filesystem\Filesystem;

class ViewsCommand extends Command {

	/**
	 * The console command name.
	 *
	 * @var string

h4cc

# Create a new Token
curl -u 'githubuser' -d '{"note":"Your Application"}' https://api.github.com/authorizations

# It is: "ebab4dc37e654bb230a9c69ebcd5f38e9a81e210"
#{
#  "created_at": "2013-01-04T18:00:28Z",
#  "app": {
#    "url": "http://developer.github.com/v3/oauth/#oauth-authorizations-api",

jbpros

var webdriver      = require("selenium-webdriver");
var launchSelenium = require("selenium-launcher");
var selenium;

launchSelenium(function (err, _selenium) {
  selenium = _selenium;
  process.on('exit', function () {
	  selenium.kill();
  });
});

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

wemakewaves

<?php

...

class DeliveryDateService extends ObjectBehavior
{
    ...
    function it_should_return_all_sundays_up_to_the_last_available_delivery_date_when_today_is_a_sunday() 
    {
        //Set the first date in the range to be Sunday, 23rd of June 2013 (16:00)

prebenlm

Irssi in Mac OS X Notification Center

Overview

This guide will explain how you can make irc messages in a screen on a remote server appear in your Mac OS X Lion Notification Center with the help of terminal-notifier.

We will also explain how the process can be automatically started each time you log in to your Mac and ensure the connection to the server is kept alive.

mikedfunk

bash cheatsheet

some stuff I still need to memorize

c-a	move to beginning of line

thelibrarian

The Problem

If you have installed the standalone Command Line Tools for XCode on your Mac (i.e. without having XCode.app installed), some of these tools can get a bit confused due to a couple of oversights on Apple's part in finalising the setup.

Note: all commands below will need to be run from an Administrator account, or by an account with appropriate permission in /etc/sudoers.

The Solution

1. Failing to Find Frameworks

Sometime when compiling against the preinstalled Frameworks (e.g. Ruby or Python), various tools will inexplicable fail to find header files that are quite clearly there. This is caused by the fact that no XCode has been selected for the command-line tools. Wait, I hear you cry, I don't have XCode installed! Indeed, but you nonetheless need to select one, and point it somewhere where the command line tools exist, like so