Haolicopter

#!/usr/bin/env python3

# Scans through your email account,
# find all the unsubscribe links in all your emails,
# and automatically opens them in a browser.

# This program will have to log in to your email provider's IMAP server
# and download all of your emails.
# You can use BeautifulSoup to check for any instance
# where the word unsubscribe occurs within an HTML link tag.

piotrklibert

typedef char C;
typedef long I;
typedef struct a {
  I t, r, d[3], p[2];
} *A;

#define P printf
#define R return

#define V1(f) A f(w)A w;

fl0w

# lazyload nvm
# all props goes to http://broken-by.me/lazy-load-nvm/
# grabbed from reddit @ https://www.reddit.com/r/node/comments/4tg5jg/lazy_load_nvm_for_faster_shell_start/

lazynvm() {
  unset -f nvm node npm npx
  export NVM_DIR=~/.nvm
  [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
  if [ -f "$NVM_DIR/bash_completion" ]; then
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion

ropiku

https://github.com/ReactiveCocoa/ReactiveCocoa

https://github.com/Alamofire/Alamofire

https://github.com/antitypical/Result

https://github.com/square/Aardvark

https://github.com/optonaut/ActiveLabel.swift

julz

package main

import (
	"fmt"
	"os"
	"os/exec"
	"syscall"
)

func main() {

shashi

twostraws

//
// loveWins(): a simple function that accepts a UIImage and
// returns the same image blended with the rainbow flag
// of the LGBT pride movement.
// 
// This is released for pedagogical reasons (I've tried to make
// the code as easy to follow as possible!) but you're welcome
// to use it for any purpose – consider the code yours.
//
// If you're using Xcode 7 / Swift 2, you need to make a tiny

christiangenco

require 'http'
require 'json'
require 'peach'
require 'gabbler'
require 'pry'

USERNAME = "patio11"

unless File.exists?("comments.txt")
  def get_json(url)

evancz

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

1. There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

aktau

#!/bin/sh
if [ "$#" -eq 1 ]; then stdinmsg=$(cat); fi
exec <"$0" || exit; read v; read v; read v; exec /usr/bin/osascript - "$@" "$stdinmsg"; exit

-- another way of waiting until an app is running
on waitUntilRunning(appname, delaytime)
    repeat until my appIsRunning(appname)
        tell application "Messages" to close window 1
        delay delaytime
    end repeat