nphyx

# Zenburn colours scheme for Xfce Terminal updated for Xfce4-terminal 0.6.3. Copy and paste the following in ${HOME}/.config/xfce4/Terminal/terminalrc:

ColorBackground=#404040
ColorForeground=#F6F3E8
ColorCursor=#8f8fafaf9f9f
ColorPalette=#3f3f3f3f3f3f;#e8e893939393;#9e9ecece9e9e;#f0f0dfdfafaf;#8c8cd0d0d3d3;#c0c0bebed1d1;#dfdfafaf8f8f;#efefefefefef;#3f3f3f3f3f3f;#e8e893939393;#9e9ecece9e9e;#f0f0dfdfafaf;#8c8cd0d0d3d3;#c0c0bebed1d1;#dfdfafaf8f8f;#efefefefefef

gregsexton

(defun company-eshell-history (command &optional arg &rest ignored)
  (interactive (list 'interactive))
  (cl-case command
    (interactive (company-begin-backend 'company-eshell-history))
    (prefix (and (eq major-mode 'eshell-mode)
                 (let ((word (company-grab-word)))
                   (save-excursion
                     (eshell-bol)
                     (and (looking-at-p (s-concat word "$")) word)))))
    (candidates (remove-duplicates

joar

# Requires fish 2.2b1 or later for the "abbr" command.
abbr -a ga="git add"
abbr -a gc="git commit"
abbr -a gco="git checkout"
abbr -a gst="git status"
abbr -a gl="git pull"
abbr -a gp="git push"
abbr -a gu="git up"
abbr -a s="git status -sb"
abbr -a l="git log"

JonathanPorta

#!/bin/bash

set -e # bail on errors

# Make sure your shell history isn't saved
hsback=$HISTFILE
unset HISTFILE

echo "Enter you current PIN - leave blank if default:"
read oldpin

djspiewak

Git DMZ Flow

I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.

• Two developers working on independent features must never be blocked by each other
  • No code freeze! Ever! For any reason!
• A developer must be able to base derivative work on another developer's work, without waiting for any third party
• Two developers working on inter-dependent features (or even the same feature) must be able to do so without interference from (or interfering with) any other parties
• Developers must be able to work on multiple features simultaneously, or at lea

alan-mushi

/*
 * A simple example of json string parsing with json-c.
 *
 * clang -Wall -g -I/usr/include/json-c/ -o json_parser json_parser.c -ljson-c
 */
#include <json.h>
#include <stdio.h>

int main() {
	struct json_object *jobj;

ibab

#ifndef ENUMS_H
#define ENUMS_H

#include <boost/preprocessor.hpp>                                                
#include <string>

/*
 * The following macros allow you to define an enum and get `toString`
 * and `fromString` functions generated automatically.
 * If you use

arudmin

#!/usr/bin/python
# -*- coding: utf-8 -*-

import os
import re
from lxml import etree
import StringIO
import sys

reload(sys)

randomphrase

#define BOOST_TEST_MODULE subcommand options
#include <boost/test/unit_test.hpp>
#include <boost/program_options.hpp>
#include <boost/variant/variant.hpp>
#include <boost/variant/get.hpp>

struct GenericOptions {
    bool debug_;
};

orls

1

    std::set phoenix;
    phoenix.key_comp();

http://www.imdb.com/title/tt0373889

2