ybakos

#!/usr/bin/env ruby
#
# Git commit-msg hook. If your branch name is in the form "t123", automatically
# adds "Refs #123." to commit messages unless they mention "#123" already.
# Include "#noref" in the message to avoid this behavior for the current commit.
# The "#noref" will be stripped from the commit message.
#
# By Henrik Nyh <http://henrik.nyh.se> 2009-09-10 under the MIT License.
#
#

ybakos

Rails CMS alternatives
======================
  Note: project activity was checked on 11/26/09 for most of these projects, and the "last update" field has not been kept up to date since then.
  
Active projects:
---------------
adva-cms
  repo: http://github.com/svenfuchs/adva_cms/
  site: http://adva-cms.org/
  Last update: 11/24/09

ybakos

alias sublime='open -a "Sublime Text 2"'

ybakos

# *&^)^(&(&&*^)^(* encoding: utf-8 *)*)&)^)^%*%&*%**
ÜglÈÊCÕnsªnt = "HAIUGLYCODEZ"
alias :send ∴; alias :get ∵
%w|rubygems sinatra|.each{|_|require _}
%w|gem load|.each{|_| ∴ _, 'kitty'}
(℧=Kitty).∴ *%w(define_method print) do |*⇧| ⇧.∴:join end
∵ %r{\/} do content_type "nialp/txet".reverse and ℧.new.random_kitty end
# gem install kitty
# ruby kitty_server.rb &
# curl http://localhost:4567

ybakos

Setting Up Clojure on OS X

I spent a lot of time trying to find a pretty optimal (for me) setup for Clojure… at the same time I was trying to dive in and learn it. This is never optimal; you shouldn't be fighting the environment while trying to learn something.

I feel like I went through a lot of pain searching Google, StackOverflow, blogs, and other sites for random tidbits of information and instructions.

This is a comprehensive "what I learned and what I ended up doing" that will hopefully be of use to others and act as a journal for myself if I ever have to do it again. I want to be very step-by-step and explain what's happening (and why) at each step.

Step 1: Getting Clojure (1.3)

ybakos

#!/usr/bin/env ruby

require 'benchmark'

REGEXPS = [
  /^no such file to load -- (.+)$/i,
  /^Missing \w+ (?:file\s*)?([^\s]+.rb)$/i,
  /^Missing API definition file in (.+)$/i,
  /^cannot load such file -- (.+)$/i,
]

ybakos

#!/bin/bash

#script extraido de: http://paulocassiano.wordpress.com/2008/08/29/deixando-o-gedit-com-a-cara-do-textmate/
#tip for better "resolution" here: http://blog.siverti.com.br/2008/05/22/fonte-monaco-no-ubuntugedit/

cd /usr/share/fonts/truetype/

#TODO: put validation if folder already exists
sudo mkdir ttf-monaco

ybakos

Sublime Text Monokai Sidebar Theme

A theme for the sidebar in Sublime Text to match the workspace of the Monokai theme.

This theme only modifies the sidebar to better match the Monokai theme, without modifying any of the styling elsewhere defined by Monokai.

File location: Packages/User

For a theme that extends beyond just the sidebar, visit https://gist.github.com/umpirsky/5842174

ybakos

#!/bin/sh

# Alot of these configs have been taken from the various places
# on the web, most from here
# https://github.com/mathiasbynens/dotfiles/blob/master/.osx

# Set the colours you can use
black='\033[0;30m'
white='\033[0;37m'
red='\033[0;31m'

ybakos

{
/* Keybindings for emacs emulation.  Compiled by Jacob Rus.
 *
 * This is a pretty good set, especially considering that many emacs bindings
 * such as C-o, C-a, C-e, C-k, C-y, C-v, C-f, C-b, C-p, C-n, C-t, and
 * perhaps a few more, are already built into the system.
 *
 * BEWARE:
 * This file uses the Option key as a meta key.  This has the side-effect
 * of overriding Mac OS keybindings for the option key, which generally