Tested in Mac OS X: super == command
Open/Goto
- super+t: go to file
- super+ctrl+p: go to project
- super+r: go to methods
var mongoose = require('mongoose') | |
, Schema = mongoose.Schema | |
, db = mongoose.connect('localhost', 'testing_streaming').connection | |
, Stream = require('stream').Stream | |
, express = require('express') | |
/** | |
* Dummy schema. | |
*/ |
if ($request_uri = /) { | |
set $test A; | |
} | |
if ($host ~* teambox.com) { | |
set $test "${test}B"; | |
} | |
if ($http_cookie !~* "auth_token") { | |
set $test "${test}C"; |
package main | |
import ( | |
"crypto/tls" | |
"crypto/x509" | |
"fmt" | |
"io" | |
"log" | |
) |
Custom recipe to get OS X 10.9 Mavericks running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install.
The software selected is software that is "tried and true" --- software I need after any fresh install. I often install other software not listed here, but is handled in a case-by-case basis.
/* ivan(a.t)mysqlab.net */ | |
package main | |
import ( | |
"syscall" | |
"os" | |
"log" | |
) | |
func daemon(nochdir, noclose int) int { |
/* | |
Developed by Robert Nyman, http://www.robertnyman.com | |
Code/licensing: http://code.google.com/p/getelementsbyclassname/ | |
*/ | |
var getElementsByClassName = function (className, tag, elm){ | |
if (document.getElementsByClassName) { | |
getElementsByClassName = function (className, tag, elm) { | |
elm = elm || document; | |
var elements = elm.getElementsByClassName(className), | |
nodeName = (tag)? new RegExp("\\b" + tag + "\\b", "i") : null, |
HTTP provides two ways for servers to control client-side caching of page components:
This breaks down as follows: