Rubyinstaller devel - Jul 2007 - [PATCH] Set pwd to \ruby\bin when running gemhelp.bat

In getting some of my colleagues to try ruby on windows, the instinct  
to install gems was to use the batch file in the start menu.  This  
file leaves you off in \ruby, so you can''t just type
''gem'' again like
the help tells you.  This patch has the bat file cd into the bin  
directory first, so the user can run ''gem''.

Thanks,
Mat

-------------- next part --------------
A non-text attachment was scrubbed...
Name: set_dir_to_ruby_bin_when_running_gem_from_bat.diff
Type: application/octet-stream
Size: 486 bytes
Desc: not available
Url :
http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20070703/3d5f7688/attachment.obj

On 7/3/07, Mat Schaffer <schapht at gmail.com>
wrote:
>
> In getting some of my colleagues to try ruby on windows, the instinct
> to install gems was to use the batch file in the start menu.  This
> file leaves you off in \ruby, so you can''t just type
''gem'' again like
> the help tells you.  This patch has the bat file cd into the bin
> directory first, so the user can run ''gem''.
>
> Thanks,
> Mat


Thanks for the patch, but I don''t understand why it is needed. The bin
directory is added to the system path on installation, so you can enter and
run the gem command no matter what directory you are in. Perhaps something
went wrong on your installation and the system path did not get updated?

Curt
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/rubyinstaller-devel/attachments/20070703/3180bfb8/attachment.html

On Jul 3, 2007, at 11:40 AM, Curt Hibbs wrote:
> Thanks for the patch, but I don''t understand why it is needed. The
> bin directory is added to the system path on installation, so you  
> can enter and run the gem command no matter what directory you are  
> in. Perhaps something went wrong on your installation and the  
> system path did not get updated?
Oh... no, sorry.  I just missed it.  I thought it would be added in  
the user path, but it''s in the system path.
Sorry! and thanks
-Mat