problem with using ruby

[Ade]

This is somewhat silly, i downloaded the 1.8.6-25 installer for windows
and installed it.
I went to the command prompt and typed ruby -v, and i got this message
saying ruby isnt a batch command recognized by windows.

What am i doing wrong? I used the one click installer.
Thanks

 

[Tim Hunter]

This is somewhat silly, i downloaded the 1.8.6-25 installer for windows
and installed it.
I went to the command prompt and typed ruby -v, and i got this message
saying ruby isnt a batch command recognized by windows.

What am i doing wrong? I used the one click installer.
Thanks

Did you try opening a new command window? I don't think changes to your
path are reflected in existing command windows, only to command windows
that you start after the change.

 

[Jano Svitok]

This is somewhat silly, i downloaded the 1.8.6-25 installer for windows
and installed it.
I went to the command prompt and typed ruby -v, and i got this message
saying ruby isnt a batch command recognized by windows.

What am i doing wrong? I used the one click installer.
Thanks

It seems it's a bug (or a feature?):

http://rubyforge.org/tracker/index.php?func=detail&aid=10655&group_id=167&atid=715

 

[Robert Klemme]

This is somewhat silly, i downloaded the 1.8.6-25 installer for windows
and installed it.
I went to the command prompt and typed ruby -v, and i got this message
saying ruby isnt a batch command recognized by windows.

What am i doing wrong? I used the one click installer.

Did you make sure that "ruby.exe" is actually reachable via %PATH%?

robert

 

[Curt (Work) Hibbs]

It seems it's a bug (or a feature?):

http://rubyforge.org/tracker/index.php?func=detail&aid=10655&group_id=167&atid=715

The linked reposrt is incorrect. That person had something go wrong
with their installation, which is probably the case hear, also. Make
sure the ruby\bin directory is on your system path.

Curt

 

[Karl von Laudermann]

The linked reposrt is incorrect. That person had something go wrong
with their installation, which is probably the case hear, also. Make
sure the ruby\bin directory is on your system path.

Speaking as the person who wrote that report, I'd say it is correct,
as it is an accurate description of what happened on my machine. On
the same machine, running the same version of Windows, version
1.8.4-19 of the one-click installer consistently adds ruby\bin to the
path (as well as doing other setup tasks), while version 1.8.6-25
consistently fails to do so. This implies that *something* is
different in the behavior between the two versions of the installer.
It may still work fine on some systems despite the difference, but I
see I'm not the only one for whom it doesn't.