From: Paul Smith Date: 2009-09-23T17:50:47+09:00 Subject: Re: How to detect what is running Ruby program? I'll admit I liked SciTE when I first came across it, and I even used it to do a live Test Driven Development demo using Ruby at the place where I work. However, I'm just happier with a command line and a good text editor. I've been using PSPad recently as we have it at work, but just use whatever your favourite editor happens to be. In this year's Google Code Jam I ditched the SciTE for a command line interface and performed much better - YMMV :) On Wed, Sep 23, 2009 at 3:13 AM, Mason Kelsey wrote: > You wrote, "...which doesn't bundle SciTE, and instead has you work from the > command line as God intended." > > Now I know why I'm an atheist!  It's that damn command line thingee! > > So are people, who like to work from the authoritarian command line, > programming fundamentalists? > > I like SciTE, it's a free IDE, even if it is of a different race.  Why can't > we all just get a lawn? > > No Sam > On Tue, Sep 22, 2009 at 6:10 AM, Paul Smith wrote: > >> On Tue, Sep 22, 2009 at 5:44 AM, Jonathan Castello >> wrote: >> > >> > Perhaps try passing a command-line argument if you're running from SciTE, >> which your program can detect and act accordingly? Assuming there's no >> simpler way, that is. >> > >> > ~Jonathan >> > >> > >> >> Date: Tue, 22 Sep 2009 13:33:23 +0900 >> >> From: masonkelsey@gmail.com >> >> Subject: How to detect what is running Ruby program? >> >> To: ruby-talk@ruby-lang.org >> >> >> >> I work on a Windows platform and have two utiltities that I can execute >> a >> >> Ruby program from.  The IDE SciTE and the fxri- Instant Ruby >> Enlightenment, >> >> or so it says.  The input commands such as "gets" do not work in the >> SciTE >> >> utility but do in the fxri utility.  If I use a gets command in a >> program >> >> while running on SciTE the system seems to freeze and nothing appears to >> be >> >> happening. >> >> IIRC there's a difference between Kernel#gets and STDIN#gets, one of >> which works from under SciTE and the other doesn't.  Try changing your >> gets call to STDIN.gets. >> >> Although personally, if you're using SciTE that probably means you're >> using the Ruby 1.8.6 one-click installer - which I would uninstall and >> move to the technology preview of Ruby 1.9, which doesn't bundle >> SciTE, and instead has you work from the command line as God intended. >> >> -- >> Paul Smith >> http://www.nomadicfun.co.uk >> >> paul@pollyandpaul.co.uk >> >> > -- Paul Smith http://www.nomadicfun.co.uk paul@pollyandpaul.co.uk