My setup: Ruby 1.8.6.p114 hand-compiled to ~/opt/ruby-1.8.6-p114.
I have a couple of other Ruby installs – Ubuntu’s Ruby 1.8.6.p111 at
the proper FHS location(s), as well as JRuby 1.1.1, Ruby 1.8.7.preview2
and Ruby 1.9.0-1 in ~/opt – but I don’t think this is the cause of the
problem.
My problem: all of a sudden, FastRI (or RI, for that matter) stopped
seeing core and stdlib classes. Running fastri-server -b and -B doesn’t
help.
At first, this problem was common to all the Ruby installs (all with
their respective FastRI gems), but I uninstalled all the fastri gems
other than the 1.8.6.p114 one and the problem persists.
-- Shot
···
--
Perl is designed for people who like oblique voodoo. For people
who have no qualms about using rhaphyrographic and tmesis, or for
that matter oblique, in casual conversation. -- Peter da Silva
Did you ever figure out what was going on here? I have the same
problem.
···
On Apr 29, 3:02 pm, "Shot (Piotr Szotkowski)" <s...@hot.pl> wrote:
My setup: Ruby 1.8.6.p114 hand-compiled to ~/opt/ruby-1.8.6-p114.
I have a couple of other Ruby installs – Ubuntu’s Ruby 1.8.6.p111 at
the proper FHS location(s), as well as JRuby 1.1.1, Ruby 1.8.7.preview2
and Ruby 1.9.0-1 in ~/opt – but I don’t think this is the cause of the
problem.
My problem: all of a sudden, FastRI (or RI, for that matter) stopped
seeing core and stdlib classes. Running fastri-server -b and -B doesn’t
help.
At first, this problem was common to all the Ruby installs (all with
their respective FastRI gems), but I uninstalled all the fastri gems
other than the 1.8.6.p114 one and the problem persists.
-- Shot
--
Perl is designed for people who like oblique voodoo. For people
who have no qualms about using rhaphyrographic and tmesis, or for
that matter oblique, in casual conversation. -- Peter da Silva
On Apr 29, 3:02 pm, "Shot (Piotr Szotkowski)" <s...@hot.pl> wrote:
My problem: all of a sudden, FastRI (or RI, for that matter) stopped
seeing core and stdlib classes. Running fastri-server -b and -B doesn’t
help.
Did you ever figure out what was going
on here? I have the same problem.
Yeah (and sorry for not following up).
What you need to do is to generate the Ruby docs with
RDoc from the Ruby source. IIRC, `rdoc -R` worked for me.
You might also want to check out the -Y
option and the rest described in `rdoc -h`.
-- Shot
--
The last time somebody said, 'I find I can write much
better with a word processor,' I replied, 'They used
to say the same thing about drugs.' -- Roy Blount Jr.