I tend to run into every conceivable error when working on a project. This afternoon I got this error when trying to commit my Rails app to subversion.

svn: Commit failed (details follow): svn: Could not use external editor to fetch log message; consider setting the $SVN_EDITOR environment variable or using the --message (-m) or --file (-F) options svn: None of the environment variables SVN_EDITOR, VISUAL or EDITOR is set, and no 'editor-cmd' run-time configuration option was found

I found out that my SVN editor environment variables were not set, so I used the -m option to tell it which editor to use and it worked. Here's the command that worked for me... svn commit -m vi

Here are 16 ways to learn Rails. I came up with this list two years ago before I had a blog. My goal is to flush out each of these items with links over the next few weeks. 1. Read "The Books"

• Agile Web Development with Rails, 2nd Edition
• The Rails Way
• Programming Ruby: The Pragmatic Programmers' Guide, Second Edition

2. Join a Club - Another way to learn Rails is to be around other people who are doing it already. There are many many Ruby and Rails clubs across the globe. If you happen live in Houston, you can join the Houston Ruby Group, which meets once a month. To find a Rails group in your area, try searching on RubyBrigade.org. Or you could start your own...

3. Convert Something 4. Participate in Forums 5. Use IRC 6. Watch "The Videos" 7. Research and Blog About It 8. Take a Class 9. Participate in a Contest - One way to learn fast is to take part in a competition. The Rails Rumble is coming up on September 20th, 2008. Hook up with some other Rails programmers and see what you can create with a 48 hour time window. 10. Work on an Open Source Project 11. Find a Tutorial and Built It 12. Listen to "The Podcasts" 13. Study the Rails Source Code 14. Goto a BarCamp 15. Subscribe to "The RSS Feeds" 16. Dissassemble an Open Source Project

It is that time again. Time to come up with resolutions that will only last a month. My main resolution is to kick the Diet Coke habit again. I'm going to do Steve Pavlina's 30 day trial. That should be easy enough... In other news, I read this interesting post from Zed Shaw called Rails is a Ghetto. In even other news, the SEC is doing fairly well in the bowls. I was disappointed in Florida for not beating Michigan. And I have no clue what happened to Arkansas. I hope LSU plays as well as Georgia did against Hawaii. It must have been shocking for Hawaii to run into The Dawgs!

As part of the TipDish project, we needed to use Rmagick to manipulate avatars. I was real sad to see it required 6+ pages of install instructions for OS X. The Windows install is MUCH simpler. I was ready to pay someone to install it for me. But I decided to just plod through the instructions. Luckily I had installed the X Windows software earlier in the year, so that cut down on the install time. It must have taken 2 hours to install. Luckily there was an exciting World Series Game on to ease the pain. I'm still not sure if I have everything configured correctly. The Rails app appears to work now.

When trying to run a Rails application recently I ran into the following error. undefined method gem for main:Object (NoMethodError) To get passed this I had to do this command: gem update --system

The Lone Star state is getting it's own Ruby conference, Lone Star Ruby Conf. This is SOOO close to Houston, I might get to go. Now I wonder if Rails will be covered.

RailsEnvy has created some really funny "Hi, I'm Ruby on Rails" commercials, comparing Rails to different web frameworks. (I first saw this at Digg.) Here's the first one. Here's the second one. Here's the third one. For the record, I like BOTH Rails and PHP...

The Houston Ruby and Rails Group meets tomorrow, May 8th at 6PM: Find out more here: http://houston-ror.pbwiki.com/Meetings