meesh mdzhang

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

agnoster.zsh-theme

A ZSH theme optimized for people who use:

Solarized
Git
Unicode-compatible fonts and terminals (I use iTerm2 + Menlo)

For Mac users, I highly recommend iTerm 2 + Solarized Dark

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

Sessions

New Session

tmux new [-s name] [cmd] (:new) - new session

Switch Session

tmux ls (:ls) - list sessions
tmux switch [-t name] (:switch) - switches to an existing session

THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.

PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

	Someone recently asked the following question in the discussion forum of the Rubyists LinkedIn group: What separates a junior Rails developer from a senior one?

	My response follows. Join us at http://www.linkedin.com/groups?gid=120725 to weigh in on this and other topics of interest to Rubyists. As of today there are almost 1,200 members, including numerous movers and shakers in the Ruby and Rails communities.

	“Distinguishing between junior and senior people in the Rails world is not so different from making the distinction in other web development environments.

	“Junior Rails people have not dealt with scaling issues to the degree that senior people have. Getting a public-facing Rails application to perform under significant stress is more challenging than doing the same with other building materials such as PHP. Senior people know how to performance-test Rails applications, where to look for bottlenecks, and how to eliminate them one after another until performance is acceptable in real conditions. The Ra

	So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

	Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

	* Off the top of my head *

	1. Fork their repo on Github
	2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

	git remote add my-fork [email protected]

	#Model

	@user.should have(1).error_on(:username) # Checks whether there is an error in username
	@user.errors[:username].should include("can't be blank") # check for the error message

	#Rendering
	response.should render_template(:index)

	#Redirecting
	response.should redirect_to(movies_path)

	# Mac OS X Lion introduced a new, iOS-like context menu when you press and hold a key
	# that enables you to choose a character from a menu of options. If you are on Lion
	# try it by pressing and holding down 'e' in any app that uses the default NSTextField
	# for input.
	#
	# It's a nice feature and continues the blending of Mac OS X and iOS features. However,
	# it's a nightmare to deal with in Sublime Text if you're running Vintage (Vim) mode,
	# as it means you cannot press and hold h/j/k/l to move through your file. You have
	# to repeatedly press the keys to navigate.