Tender Lovemaking

February 2016

I am a puts debuggerer

December 2015

Inline caching in MRI

February 2015

January 2015

My experience with Minitest and RSpec

June 2014

March 2014

Webcam photos with Ruby

February 2014

January 2014

Enabling ttyO1 on BeagleBone

May 2013

One Danger of Freedom Patches

March 2013

Dynamic Method Definitions

February 2013

YAML f7u12

December 2012

Rails 4 and your Gemfile

September 2012

Protected Methods and Ruby 2.0

July 2012

June 2012

Removing config.threadsafe!

February 2012

Ten Years of Nerd Club

January 2012

My Jerky Setup

December 2011

Profiling Rails startup with DTrace

November 2011

PSA: The number of gems installed on your system can impact rails boot time

October 2011

Connection Management in ActiveRecord

June 2011

March 2011

Rack API is awkward

January 2011

December 2010

April 2010

January 2010

Compiling with Clang

December 2009

October 2009

Full Text Search on Heroku

September 2009

Ruby and RFID tags

June 2009

May 2009

April 2009

February 2009

December 2008

Nokogiri’s Slop Feature

November 2008

October 2008

Nokogiri Is Released

September 2008

Mushrooms, Beef Jerky, and Programming

August 2008

Identifying unknown music with Ruby

July 2008

Back Home!

June 2008

Meow meow meow meow meow

May 2008

Write your Rails view in……. JavaScript?

April 2008

March 2008

February 2008

January 2008

December 2007

November 2007

October 2007

September 2007

August 2007

July 2007

June 2007

May 2007

April 2007

March 2007

February 2007

January 2007

December 2006

November 2006

October 2006

September 2006

August 2006

July 2006

June 2006

May 2006

Read more at the source

Bundler problem: “You have already activated launchy 0.3.7″

March 11, 2011

I just wanted to post this in case anyone else is getting a weird error saying “You have already activated launchy 0.3.7. Consider using bundle exec.” – even though you are already using bundle exec. Here is the full error message:

/usr/bin/ruby1.9.1 -S bundle exec rspec ...
/var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/runtime.rb:31:in `block in
  setup': You have already activated launchy 0.3.7, but your Gemfile requires
  launchy 0.4.0. Consider using bundle exec. (Gem::LoadError)
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/spec_set.rb:12:in `block in each'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/spec_set.rb:12:in `each'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/spec_set.rb:12:in `each'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/runtime.rb:17:in `setup'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler.rb:109:in `setup'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/cli.rb:307:in `exec'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/vendor/thor/task.rb:22:in `run'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/vendor/thor.rb:246:in `dispatch'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/lib/bundler/vendor/thor/base.rb:389:in `start'
        from /var/lib/gems/1.9.1/gems/bundler-1.1.pre.1/bin/bundle:13:in `<top (required)>'
        from /var/lib/gems/1.9.1/bin/bundle:19:in `load'
        from /var/lib/gems/1.9.1/bin/bundle:19:in `<main>'
rake aborted!
ruby -S bundle exec rspec ... failed

This can happen if your gem or app is requiring launchy and you have version 0.4.0 installed on your system. The open_gem gem (which you are perhaps not even using, but it’s being auto-loaded anyway by rubygems) requires launchy ~> 0.3.5 (meaning, 0.3.5 or 0.3.7), but because it’s loaded outside of Bundler, when Bundler runs and calculates your dependencies, it does not take this into account and simply records version 0.4.0 in your Gemfile.lock. And then when you try to load your app or gem, it balks because 0.3.5 or 0.3.7 has already been loaded by open_gems.

The “obvious” solution is to fix your app to require launchy ~> 0.3.5 as well so it won’t try to load version 0.4.0, but once open_gem gets fixed to work with version 0.4.0, you will just have this problem the other way around, with open_gem loading version 0.4.0, and your app trying to load 0.3.7.

Uninstalling launchy 0.4.0 from your system won’t work either, because Bundler will simply reinstall it when you rerun bundle install (even after you’ve deleted your Gemfile.lock).

For me, the only way to solve this problem was to uninstall open_gem:

1	`sudo gem uninstall open_gem`

It will also tell you about breaking dependencies – in my case, I’ve had to uninstall guard beforehand.

Now open_gem does not get loaded anymore, and requiring launchy 0.4.0 works fine again.

..and on the seventh day, Science created zsh

August 31, 2009

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. ;-)