Emmanuel Lazarte neverkas

Problem

I have two Github accounts: oanhnn (personal) and superman (for work). I want to use both accounts on same computer (without typing password everytime, when doing git push or pull).

Solution

Use ssh keys and define host aliases in ssh config file (each alias for an account).

How to?

Generate ssh key pairs for accounts and add them to GitHub accounts.

GNU Make Cheatsheet

Based on https://www.gnu.org/software/make/manual/html_node/Quick-Reference.html

Directives

Directive	Description
`define variable` `define variable =` `define variable :=` `define variable ::=` `define variable +=` `define variable ?=` `endef`	Define multi-line variables.
`undefine variable`	Undefining variables.

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Screen Quick Reference

Basic

Description	Command
Start a new session with session name	`screen -S <session_name>`
List running sessions / screens	`screen -ls`
Attach to a running session	`screen -x`
Attach to a running session with name	`screen -r`

emacs --daemon to run in the background. emacsclient.emacs24 <filename/dirname> to open in terminal

NOTE: "M-m and SPC can be used interchangeably".

Undo - C-/
Redo - C-?
Change case: 1. Camel Case : M-c 2. Upper Case : M-u

Lower Case : M-l

This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.

Running your own encrypted chat service with Matrix and Riot

Workshop Instructor:

Lilly Ryan @attacus_au

This workshop is distributed under a CC BY-SA 4.0 license.

What are we doing here?

If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".

Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".

You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".

Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.

Go to the relevant commit: git checkout v4.7.4
Create a new branch from it: git checkout -b 4.x (You can choose any branch name, just make sure to use the same in step 3)

	#!/usr/bin/env sh


	## Set newt color palette for dialogs
	NEWT_COLORS_0='
	root=,blue
	'
	NEWT_COLORS_1='
	root=,blue
	checkbox=,blue

	(ns apples.core
	(:require [play-clj.core :refer :all]
	[play-clj.g2d :refer :all]
	[play-clj.math :refer :all]))

	(declare apples main-screen)
	(def speed 14)

	(defn- get-direction []
	(cond

	wget --no-check-certificate --content-disposition https://github.com/joyent/node/tarball/v0.7.1
	# --no-check-cerftificate was necessary for me to have wget not puke about https
	curl -LJO https://github.com/joyent/node/tarball/v0.7.1