From: Phlip <phlip2005@...>
Date: 2009-02-23T13:19:40+09:00
Subject: Re: Help/Cannot Open Ruby Project in Ide

Zayd Connor wrote:

> Yeah this does suck, unfortunately I dont know how to run a rake task 
> yet, this would be a great time to learn how to, also this is a rails 
> project so I know it could be a bit harder using Scite as opposed to 
> using an Ide like Netbeans. I do need to start getting more familiar 
> with the command prompt, so using Scite would be a good experience. I 
> can build a rails project with Scite right?

Unlike some platform we could mention, you cannot do Ruby without learning to 
use a command line. Some platforms exploit "vendor lock-in", so their language 
forces you to use their editor!

I use Kate, and a command line I wrote, trigger.rb, which runs rake test:recent 
whenever any code changes. Then I map Kate's <f5> to save all files. I leave the 
editor over the console, so I can see both, and I just

Even the mighty TextMate cannot accomplish that simple envelop, and I have 
absolutely no idea why it can't.

Scite will run the current file when you hit <f5>. I use that for _non_ Rails 
scripts, because running the current file is probably what you _don't_ want. I 
should not have recommended it, except I'm in the habit of putting this icky 
line at the bottom of each file:

   system 'ruby test:recent' if $0 == __FILE__

-- 
   Phlip

http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html