Could you provide more details on how gem "gets an error"? I just tried it (including installing gems from IRB) and it worked fine. This isn't the first heisenbug that I've seen with Ruby and Windows... (for instance, see http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/36be3d7767f66300/9b14c8774d0a5159 )
Thanks, --Matt Jones On May 19, 11:53 am, Umur Ozkul <[email protected]> wrote: > Matt Jones wrote: > > Have you tried invoking gem as `gem.bat --version` in IRB? There's a > > special case in the config.gem installation code for win32, so I'd > > guess that that might solve your problem... > > > --Matt Jones > > > On May 19, 6:32 am, Umur Ozkul <[email protected]> > > Yes, I tried. > > gem.bat itself is invoking but the calls it makes are resulting all in > errors. > Basically, in IRB, we could not call any "gem installed" commands in > Windows. > > e.g. gem, rails, rake > > The mystery is as they are available in Shell, why they do result in > error called from IRB? > > So far 4 other people complained me of the same thing. > > I am inclined to conclude that nobody uses IRB on Windows :) > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
