dearmark

rustup component add rust-src
export RUST_SRC_PATH="$(rustc --print sysroot)/lib/rustlib/src/rust/src"

ghassanpl

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

#define TYPE_VALUEARRAY 0
#define TYPE_POINTERARRAY 1

typedef struct value
{
	long Type, Rank, Dimensions[3], Elements[2];

boydc7

# push relevant tags when pushing branches
git config --global push.followTags true

# Make git pull do a --recurse-submodules flag on each pull
git config --global submodule.recurse true

# Make git push do an on-demand try of pushing sub-modules before pushing main repos
git config --global push.recurseSubmodules on-demand

# push only current branch on a push

ninrod

Solarized Dark values on different color palettes

SOLARIZED	HEX	16/8	TERMCOL	XTERM	HEX	L*A*B	RGB	HSB	GNU screen
base03	#002b36	8/4	brblack	234	#1c1c1c	15,-12,-12	0,43,54	193,100,21	K
base02	#073642	0/4	black	235	#262626	20,-12,-12	7,54,66	192,90,26	k
base01	#586e75	10/7	brgreen	240	#585858	45,-07,-07	88,110,117	194,25,46	G
base00	#657b83	11/7	bryellow	241	#626262	50,-07,-07	101,123,131	195,23,51	Y
base0	#839496	12/6	brblue	244	#808080	60,-06,-03	131,148,150	186,13,59	B
base1	#93a1a1	14/4	brcyan	245	#8a8a8a	`65,-05

yrevar

{0: 'tench, Tinca tinca',
 1: 'goldfish, Carassius auratus',
 2: 'great white shark, white shark, man-eater, man-eating shark, Carcharodon carcharias',
 3: 'tiger shark, Galeocerdo cuvieri',
 4: 'hammerhead, hammerhead shark',
 5: 'electric ray, crampfish, numbfish, torpedo',
 6: 'stingray',
 7: 'cock',
 8: 'hen',
 9: 'ostrich, Struthio camelus',

joshisumit

'''
HTTP Reuests has following parameters: 
1)Request URL 
2)Header Fields
3)Parameter 
4)Request body
'''
#!/usr/bin/env python

import requests

lwhjp

#lang racket

;;
;; These are some examples of different ways to compute factorials
;; using various paradigms and features provided by Racket. There
;; are more options available in packages which are not imported
;; by default, but that rabbit hole goes very deep indeed.
;;
;; Comments and suggestions welcome!
;;    [email protected]

Lazza

This script is NOT MAINTAINED

This snippet of code was posted in 2014 and slightly revised in 2016 and 2017. It was more of a quick'n'dirty script than a polished tool. It is made only for Linux and in Python 2, which has since become outdated.

I currently do not use it, and I suggest you avoid it as well. Please do not expect support for using this script.

🔥 If you need an alternative, @glaucocustodio has kindly suggested EasyVPN in this comment.

The rest of the README is left for historical purposed.

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

ViViDboarder

#! /bin/bash

# Make a directory to hold local libs and bins
mkdir -p ~/usr/local

# Get protobuf
wget https://protobuf.googlecode.com/files/protobuf-2.5.0.tar.gz
# Extract protobuf
tar -xvzf protobuf-2.5.0.tar.gz
cd protobuf-2.5.0