reu

var redis = require("redis")
  , subscriber = redis.createClient()
  , publisher  = redis.createClient();

subscriber.on("message", function(channel, message) {
  console.log("Message '" + message + "' on channel '" + channel + "' arrived!")
});

subscriber.subscribe("test");

kevin-smets

Default

Powerlevel10k

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

magnetikonline

AWS S3 bucket and IAM policy recipes

• Recipes
  • Anonymous GET access
  • Anonymous GET access - match HTTP referrer
  • Full access for specific IAM user/role
  • GET/PUT/DELETE access to specific path within a bucket
  • Restricted LIST & PUT/DELETE access to specific path within a bucket
  • Full access (and S3 console) for specific IAM users
  • Bucket and object delete deny

gaearon

  configureDragDrop(registerType) {
    var imageThreshold = Math.max(120, window.innerHeight / 4),
        sectionThreshold = Math.max(140, window.innerHeight / 4),
        currentDY = 0,
        frame;

    function makeScrollingHandler(threshold) {
      function getScrollDY(clientY) {
        var speed;
        if (clientY < threshold) {

miguelmota

function randomDate(start, end) {
  return new Date(start.getTime() + Math.random() * (end.getTime() - start.getTime()))
}

console.log(randomDate(new Date(2012, 0, 1), new Date()))

peteroupc

/*
Written by Peter O.

Any copyright to this work is released to the Public Domain.
In case this is not possible, this work is also
licensed under Creative Commons Zero (CC0):
https://creativecommons.org/publicdomain/zero/1.0/

*/

paulirish

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

haskellcamargo

String.prototype.chunkBy = function(len) {
  var current = len;
  var previous = 0;
  var stack = [];

  while (this[current]) {
    if (this[current++].match(/s+/)) {
      stack.push(this.substring(previous, current));
      previous = current;
      current += len;

daniellmb

(function($) {
  var result = $('#result');
  var base = $('#base');
  var list = $('#list');
  $('#calc').click(function() {
    var baseVal = base.val();
    var px = list.val().split(',');
    var html = [];
    $.each(px, function(i, v) {
      var px = parseInt(v);