Clint Plummer yuhonas

Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118

Your problem with Vim is that you don't grok vi.

You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).

The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:

0 go to the beginning of this line. y yank from here (up to where?)

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

Mac web developer apps

This gist's comment stream is a collection of webdev apps for OS X. Feel free to add links to apps you like, just make sure you add some context to what it does — either from the creator's website or your own thoughts.

— Erik

Zsh Tips and Tricks

Argument History

!*        # ... All parameters of the last command
!$        # ... Last parameter of the last command
!^        # ... First parameter of the last command
!:1       # ... First parameter of the last command

!-2:2 # ... Second parameter from 2 commands ago

This gist was writen in 2012 and it was solving specific problem in Rails & SimpleForm. Some fellow developers were pointing out this may be out dated concept. That's why I advise everyone to read comment section bellow to have a full grasp of alternative solutions

other sources that may be helpful to understand why this may not be best idea:

Why Ruby doesn’t have a Boolean class

Project Name

TODO: Write a project description

Installation

TODO: Describe the installation process

	#
	# mmm m m mmm mmm mmm mmmmm mmm
	# " # "m m m" #" # # " #" "# # # # #" #
	# m"""# #m#m# #"""" """m # # # # # #""""
	# "mm"# # # "#mm" "mmm" "#m#" # # # "#mm"
	#
	# nginx configuration For Ruby/Rack web applications
	#
	# Cooked up with style, care and a bit of secret
	# nerdy spice. :-)

	# inspired by http://ariejan.net/2010/08/23/resque-how-to-requeue-failed-jobs

	# retry all failed Resque jobs except the ones that have already been retried
	# This is, for instance, useful if you have already retried some jobs via the web interface.
	Resque::Failure.count.times do \|i\|
	Resque::Failure.requeue(i) unless Resque::Failure.all(i, 1)['retried_at'].present?
	end

	# retry all :)
	Resque::Failure.count.times do \|i\|

	#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)