virasak

/*
 * The author disclaims copyright to this source code.  In place of
 * a legal notice, here is a blessing:
 * 
 *    May you do good and not evil.
 *    May you find forgiveness for yourself and forgive others.
 *    May you share freely, never taking more than you give.
 *
 */
package org.hibernate.dialect;

ry

/*
   A simple new-line delimited JSON protocol with upgrades.

   Receiving Usage:

     protocol = require('./frame-protocol');

     // parsing data
     parser = protocol.Parser();

lucasfais

Sublime Text 2 – Useful Shortcuts (Mac OS X)

General

⌘T	go to file
⌘⌃P	go to project
⌘R	go to methods
⌃G	go to line
⌘KB	toggle side bar
⌘⇧P	command prompt

Abizern

//
//  NSData+Base64.h
//  base64
//
//  Created by Matt Gallagher on 2009/06/03.
//  Copyright 2009 Matt Gallagher. All rights reserved.
//
//  This software is provided 'as-is', without any express or implied
//  warranty. In no event will the authors be held liable for any damages
//  arising from the use of this software. Permission is granted to anyone to

marcellodesales

/*
 * The plugins used for this build.
 */
/*
 * Provides the compile, test, jar, etc tasks
 */
apply plugin: 'java'

/*
 * Generates the Eclipse project files.

marktheunissen

This playbook has been removed as it is now very outdated.

dlecocq

# Environment
#
#     export HOSTNAME=...
#     export CLUSTER=...
#     export RACK=...
#     export ESDIR=
#     export AWS_ACCESS_KEY=...
#     export AWS_SECRET_KEY=...

# Packages

rgbkrk

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

'''
Wrote this very fast to quickly mirror nodejs's dist directory, which nvm
(the node version manager) uses to pull releases of node.

If nodejs.org provided rsync access (or other means), I would have
just mirrored it that way.

kagemusha

version: grunt-cli v0.1.8


1. Install node-inspector globally (-g)

    npm install -g node-inspector

2. Add debugger statements to your code

3. Run your grunt task in debug mode

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions