Forum: Ruby on Rails Strange IRB problem

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
9a167f5cc00e676a74346cc647d59d94?d=identicon&s=25 Doug (Guest)
on 2009-02-07 02:08
(Received via mailing list)
very strange....
I'm on Vista and updated to Rails 2.2.2 and rubygems 1.3.1 with the
usual problem there.
...but that's well documented...

everything was fine....but then I tried the irb console.
in every shell I have (netbeans, git bash, windows shell)
I got this result:

-----------------------------------------------------------------------------------------
Doug@APOLLO /c/projects/work/MathCraze
$ script/console
Loading development environment (Rails 2.2.2)

c:\projects\work\MathCraze>#@echo off
'#@echo' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#goto endofruby
'#goto' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#!/bin/ruby
'#!' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#   irb.rb - intaractive ruby
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#    $Release Version: 0.9.5 $
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#    $Revision: 1.2.2.1 $
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#    $Date: 2005/04/19 19:24:56 $
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#    by Keiju ISHITSUKA(keiju@ruby-
lang.org)
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>#
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\projects\work\MathCraze>require "irb"
'require' is not recognized as an internal or external command,
operable program or batch file.
The syntax of the command is incorrect.
c:\projects\work\MathCraze>if __FILE__ == $0
-----------------------------------------------------------------------------------------------------------------

In Netbeans (6.5), while the Rails Console gives similiar output,
however,
the Ruby IRB sort of "worked", but I had to load the environment
manually.
 ...see below...

=======================================================================
.irbrc successfully loaded
>> load 'config/environment.rb'
load 'config/environment.rb'

=> true
>> u = User.new
u = User.new

=> #<User id: nil, login: nil, crypted_password: nil, password_salt:
nil, persistence_token: nil, login_count: nil, last_request_at: nil,
last_login_at: nil, current_login_at: nil, last_login_ip: nil,
current_login_ip: nil, created_at: nil, updated_at: nil>
>> f = FlashCardGame.new
f = FlashCardGame.new

=> #<FlashCardGame:0x5c86d4c @y=98, @x=75, @answer=173>
>>

=====================================================================

ANY Ideas?
3131fcea0a711e5ad89c8d49cc9253b4?d=identicon&s=25 Julian Leviston (Guest)
on 2009-02-07 04:54
(Received via mailing list)
Don't u need to type ruby in front of ruby scripts on windows!?

Blog: http://random8.zenunit.com/
Learn rails: http://sensei.zenunit.com/
9a167f5cc00e676a74346cc647d59d94?d=identicon&s=25 Doug (Guest)
on 2009-02-07 06:00
(Received via mailing list)
On Feb 6, 7:53 pm, Julian Leviston <jul...@coretech.net.au> wrote:
> Don't u need to type ruby in front of ruby scripts on windows!?
>
> Blog:http://random8.zenunit.com/
> Learn rails:http://sensei.zenunit.com/
>

Yeah, I used to have to do that.....especially in the DOS shell.
not sure why that changed.

but in this case it doesn't make any difference.
This topic is locked and can not be replied to.