gosukiwi

Common Lisp Cheatsheet

Common Lisp is a general-purpose programming language with functions as first-class citizens. Don't worry about being purely functional, Lisp is Object Oriented too. CLOS is a very powerful object-oriented system!

Useful definitions

The Common Lisp lingo is quite unique:

• Package: Basically a namespace, a place for symbols to live
• System: Basically a Library. A bunch of code plus some instructions how it should be treated, for example which other systems it depends on, what should be loaded and/or compiled first, etc. Not in ANSI lisp but widespread. The most common system definition tool is ASDF.
• Modules: Deprecated and implementation-dependent
• Quicklisp: Like NPM or Ruby Gems for ASDF Systems.

redrick

#Model 

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

#Rendering
expect(response).to render_template(:index)

#Redirecting 
expect(response).to redirect_to(movies_path)

phansch

NOTE: This is outdated. Check the comments below for more up-to-date forks of this gist.

Improved YARD CHEATSHEET http://yardoc.org

forked from https://gist.github.com/chetan/1827484 which is from early 2012 and contains outdated information.

• Official Getting Started Guide
• Official Tags documentation
• Type naming examples

gosukiwi

Usage: zf PATTERN [DIR]

Example: zf foo app/

Paste this somewhere. I use it in /usr/local/bin. Remeber to chmod +x /usr/local/bin/zf.

if [ -z "$1" ]
  then
 echo "usage: zf PATTERN [DIR]"

gosukiwi

alpha_sapphire is a toy programming language concept. Designed for minimal syntax and fully object-oriented expressiveness a-la Smalltalk and Ruby.

Things trying to archieve:

• Everything should be an object
• Meta-programming should be easy
• Syntax shold be minimal yet expressive
• Should be inspired by Smalltalk and Ruby
• Should give the power to the programmer, not limit him

bpierre

Switch To Vim For Good

NOTE: This guide has moved to https://github.com/bpierre/switch-to-vim-for-good

This guide is coming from an email I used to send to newcomers to Vim. It is not intended to be a complete guide, it is about how I switched myself.

My decision to switch to Vim has been made a long time ago. Coming from TextMate 1, I wanted to learn an editor that is Open Source (so I don’t lose my time learning a tool that can be killed), cross platform (so I can use it everywhere), and powerful enough (so I won’t regret TextMate). For these reasons, Vim has always been the editor I wanted to learn, but it took me several years before I did it in a way that works for me. I tried to switch progressively, using the Janus Vim distribution for a few months, then got back to using TextMate 2 for a time, waiting for the next attempt… here is what finally worked for me.

Original gist with comments: https://gist.github.com/bpierre/0a0025d348b6001394e0

romainl

This gist is no longer maintained.

See https://github.com/romainl/vim-rnb for an up-to-date version.

---

My Vim-related gists.

mlr

# Model

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

# Rendering

expect(response).to render_template(:index)

# Redirecting

tomas-stefano

Capybara Actions

# Anchor
click_link 'Save'

# Button
click_button 'awesome'

# Both above

pnathan

(defmacro clj-hash (&rest kvs)
  "Destructures `kvs`: assums keys and values are paired together:

kvs ::= k1 v1 ... kn vn

Defines a sequence of functions ki that will obtain the value of ki
from a hash table.

Raises simple-error on ki not being a keyword.