bgror

Join the zsh revolution »

Created at: 27.05.2010 20:17, source: Robby on Rails, tagged: zsh ohmyzsh console terminal bash

I love the OhMyZsh community. Let’s grow it a little more this next Tuesday.

Join the Zsh revolution here…

Double Shot #646 »

Created at: 11.02.2010 13:50, source: A Fresh Cup, tagged: Double Shot bash cerberus git iPhone os x PostgreSQL ripple

Another semi-random walk through my corner of the internet.

• ripple - Ruby client for the Riak distributed database.
• Cerberus 0.7.5 Released - New version of the Ruby CI server that I'm happiest with at the moment, now with Mercurial support.
• GLTerminal - If OS X leaves you pining for the distorted fuzzy green-screen thin clients of yore, this little piece of freeware is the cure.
• Turn Off Google Buzz With One Click - Really, the only thing you need to know.
• The iPhone obsession - Doomed argument that web devs should care about standards instead of candy.
• Easiest Postgres Install Ever - Mac Edition - Script from Wayne Seguin, passed on by Philip Ingram.
• Git Autocomplete in Mac OS X - A tiny little bit of shell convenience. If you use the Git for OS X Installer, you already have the script on your drive.
• HoudahSpot - Search/Find utility for OS X that actually finds what I'm looking for, unlike Spotlight. Yeah, if I was a Spotlight pro there are probably commands to do all this. It's easier to spend money than time, though.
• rake_cap_bash_autocomplete - More autocomplete fun for bash. A bit slow though on my Mac.

Oh My Zsh gets an auto-updater »

Created at: 01.10.2009 05:21, source: Robby on Rails, tagged: programming zsh bash terminal project

I wanted to publically thank everyone for helping me get Oh My Zsh out there and continue to improve it. Many of us spend a lot of time in our terminals throughout the day and I firmly believe that having a well-working shell is nearly as important as having a well-working texteditor.

While Oh My Zsh isn’t a large project, it is my attempt to share what I’ve learned about using zsh with others… but honestly, my goal is to learn from you. I don’t have a lot of time to really dive into the deepend of the zsh-pool so am relying on others to share their tricks, hacks, functions, themes, etc. So, I thought that if I created a basic framework with outlined some conventions so that others could contribute, that perhaps I’d end up with a kickass shell.

So far… Oh My Zsh has been forked on github 25 times and is being watched by over 100 people.

Last week, I pushed out an update that introduces an auto-update feature. I’m quite keen of desktop applications that can auto-update themselves, so our initial version of this feature will ask you no more than once a week if you want to check for updates. This means that as we continue to extend and improve Oh My Zsh, you can keep up-to-date.

Uploaded with plasq’s Skitch!

It’s the beginning of a new month… are you still using Bash? Perhaps you’re using your own zsh configuration but want to see what else zsh can offer you? I invite you to install Oh My Zsh today. :-)

Just run this in your terminal and you’ll get setup. Don’t worry… you won’t lose your existing configuration. :-)

wget http://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh -O - | sh

For more infromation, visit http://github.com/robbyrussell/oh-my-zsh/

..and on the seventh day, Science created zsh »

Created at: 31.08.2009 04:08, source: Robby on Rails, tagged: programming terminal osx linux console bash zsh git github commandline

Inspired by some recent posts from Tom on zsh, I decided that I’d do my part to help people give it a whirl. I’ve been using zsh for a few years now and haven’t found myself missing bash.

If you’re interested in taking a few minutes to give zsh a while, you’re in luck. I recently reorganized all of my zsh config into a package and tossed it on github to share. My goal was to create a reusable tool that would allow people to get up and running quickly with some of the fun configuration that I’ve come to rely on on a daily basis.

For example:

• Auto-complete rake and capistrano tasks
• Git branch names when you’re in a git project directory structure
• Tons of color highlighting (grep, git, etc.)
• Sexy prompts.. (so say me)
• much much more…

I invite you to give Oh My Zsh a whirl, which should take you less than a minute. Just follow the instructions.

Also, Oh My Zsh is Snow Leopard compatible. ;-)

Git commit-msg for Lighthouse tickets »

Created at: 16.02.2009 21:51, source: Robby on Rails, tagged: programming git lighthouse github workflow bash

A quick follow-up to a post from a few months ago on how our team has a naming convention for git branches when we’re working on Lighthouse tickets (read previous post).

I’ve just put together a quick git hook for commit-msg, which will automatically amend the commit message with the current ticket number when you’re following the branch naming conventions described here.

Just toss this gist into .git/hooks/commit-msg.

  #!/bin/sh

  #
  # Will append the current Lighthouse ticket number to the commit message automatically
  # when you use the LH_* branch naming convention.
  #
  # Drop into .git/hooks/commit-msg
  # chmod +x .git/hooks/commit-msg

  exec < /dev/tty

  commit_message=$1
  ref=$(git symbolic-ref HEAD 2> /dev/null) || return
  branch=${ref#refs/heads/}

  if [[ $branch =~ LH_(.*) ]]
  then
  lighthouse_ticket=${BASH_REMATCH[1]}

    echo "What is the state of ticket #${lighthouse_ticket}? " 
    echo "(o)pen " 
    echo "(h)old" 
    echo "(r)esolved" 
    echo "Enter the current state for #${lighthouse_ticket}: (o)" 

    state="open" 

    read state_selection

    case $state_selection in
      "o" )
        state="open" 
        ;;
      "h" )
        state="hold" 
        ;;
      "r" )
        state="resolved" 
        ;;
    esac
  echo >&2 "[#${lighthouse_ticket} state:${state}]" >> "$1" 
    exit 0
  fi

Then a quick example of how this works…

  ➜  bin git:(LH_9912 ♻ ) git ci -m "another test" 
  What is the state of this ticket? 
  (o)pen 
  (h)old
  (r)esolved
  Enter the current state: (o)
  h
  Created commit 1ed2713: another test
   1 files changed, 3 insertions(+), 1 deletions(-)

Now to see this in action… (screenshot)

Then we’ll check out the git log really quick.

➜  bin git:(LH_9912) git log
commit 1ed271323c4a054fe56e76bddc9ac81d241a1032
Author: Robby Russell <robby@planetargon.com>
Date:   Mon Feb 16 12:06:33 2009 -0800

    another test
    [#9912 state:hold]

Thanks to Andy for helping me figure out how to read user input during a git hook.