moki9

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 list is provided as a guide for tools engineers of all skill levels looking for jobs in the game industry. It's meant as a guide to topics that should be pursued broadly in order to be well spoken in an interview. I doubt any hiring manager requires deep knowedge across every topic, but an ideal candidate would be somewhat knowledgable (aware of its existence if asked directly) with all topics here.

Each list of bullets increases in difficulty, so later bullets are more applicable to senior (or even director) level candidates.

Good luck.

@gorlak

Math

To remove a submodule you need to:

Delete the relevant section from the .gitmodules file.
Stage the .gitmodules changes git add .gitmodules
Delete the relevant section from .git/config.
Run git rm --cached path_to_submodule (no trailing slash).
Run rm -rf .git/modules/path_to_submodule (no trailing slash).
Commit git commit -m "Removed submodule "
Delete the now untracked submodule files rm -rf path_to_submodule

NERDTree

o.......Open files, directories and bookmarks....................|NERDTree-o|
go......Open selected file, but leave cursor in the NERDTree.....|NERDTree-go|
t.......Open selected node/bookmark in a new tab.................|NERDTree-t|
T.......Same as 't' but keep the focus on the current tab........|NERDTree-T|
i.......Open selected file in a split window.....................|NERDTree-i|
gi......Same as i, but leave the cursor on the NERDTree..........|NERDTree-gi|
s.......Open selected file in a new vsplit.......................|NERDTree-s|
gs......Same as s, but leave the cursor on the NERDTree..........|NERDTree-gs|

O.......Recursively open the selected directory..................|NERDTree-O|

Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.

For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai

	SPC s c remove highlight

	**** Files manipulations key bindings
	Files manipulation commands (start with ~f~):

	\| Key Binding \| Description \|
	\|-------------+----------------------------------------------------------------\|
	\| ~SPC f c~ \| copy current file to a different location \|
	\| ~SPC f C d~ \| convert file from unix to dos encoding \|
	\| ~SPC f C u~ \| convert file from dos to unix encoding \|

	#!/bin/bash
	set -e

	GVERSION="1.8.3"
	GFILE="go$GVERSION.linux-amd64.tar.gz"

	GOPATH="$HOME/projects/go"
	GOROOT="/usr/local/go"
	if [ -d $GOROOT ]; then
	echo "Installation directories already exist $GOROOT"

	# Make sure you grab the latest version
	curl -OL https://github.com/google/protobuf/releases/download/v3.2.0/protoc-3.2.0-linux-x86_64.zip

	# Unzip
	unzip protoc-3.2.0-linux-x86_64.zip -d protoc3

	# Move protoc to /usr/local/bin/
	sudo mv protoc3/bin/* /usr/local/bin/

	# Move protoc3/include to /usr/local/include/