ri odd behavior

[Jean-Julien Fleck]

Hello,

How would you correct this "bug" in ri ?

~> ri Object#tap
More than one method matched your request. You can refine
your search by asking for information on one of:

Object#tap, Object#tap

There seem to be no difference between the two proposed strings so I
have no way to access either one of them.

Cheers,


--=20
JJ Fleck
PCSI1 Lyc=E9e Kl=E9ber

 

[Ricardo Panaggio]

Hello,

How would you correct this "bug" in ri ?

~> ri Object#tap
More than one method matched your request. You can refine
your search by asking for information on one of:

=A0 =A0Object#tap, Object#tap

Trunk is ok. I've tested it here and it doesn't show that bug.

Could you send the ruby version you're using, so that this can be tracked?

$ ruby -v
ruby 1.9.3dev (2010-07-21 trunk 28695) [x86_64-linux]
$

 

[Jean-Julien Fleck]

Hello,

Could you send the ruby version you're using, so that this can be tracked= ?

$ ruby -v
ruby 1.9.3dev (2010-07-21 trunk 28695) [x86_64-linux]

Sure:

~>ruby -v
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]

Could it be some installed gem that override the Object#tap method and
confuse ri ?

Thanks,


--=20
JJ Fleck
PCSI1 Lyc=E9e Kl=E9ber

 

[Ryan Davis]

Hello,

Could you send the ruby version you're using, so that this can be tracked?

$ ruby -v
ruby 1.9.3dev (2010-07-21 trunk 28695) [x86_64-linux]

Sure:

~>ruby -v
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]

Could it be some installed gem that override the Object#tap method and
confuse ri ?

you have 2 installs of the rdoc/ri info. Do this:

% locate cdesc-Array.yaml | grep system