From: Peter Bailey <lists@...>
Date: 2013-05-08T19:59:20+09:00
Subject: Re: can't find gems

tamouse mailing lists wrote in post #1108166:
> On Tue, May 7, 2013 at 8:01 AM, Peter Bailey <lists@ruby-forum.com>
> wrote:
>>>> Also, try running that script without the file name argument.
>>
> 
/home/tamara/.rvm/rubies/ruby-1.9.3-p392/lib/ruby/site_ruby/1.9.1/rubygems.rb:1073
>>> So, it's not a 2.0 problem. It may not be a problem at all, as all -d
>>> is doing is setting the $DEBUG global to true, AFAICT. (If you're
>>> expecting that to launch in debug mode, that won't do it. Try pry
>>> instead.)
>>
>> Thanks.
>> I get hello, world with your suggestion.
>> Yes, the file is indeed there. If I run it without a "-d," I get a "no
>> implicit conversion of nil into string" error.
>
> My first suggestion is dump the -d; it's not doing what you think, and
> obviously masking another error. Look at the backtrace from that error
> and find out where it's happening, and trace it back to your code.
>
> You might want to look at pry for a pretty nice debugger, but the ruby
> debugger works decently. You have to insert it into your code though,
> this is NOT done by using -d on the command line.
>
> Use gem or bundler to install the debugger, then place the following
> in your file:
>
>     require 'debugger'
>     debugger
>
> That will call the debugger at the beginning and you can walk through.

Thanks. I think I've got it now. I had to install the Dev_Kit, properly. 
That wasn't easy.

Cheers.

-- 
Posted via http://www.ruby-forum.com/.