Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to get Ruby to work (on .gitbook)?
    text
    copied!<p>I'm trying to get Ruby to run so that I can draft a contribution to the Git Community Book.</p> <p>I'm on windows XP. I've downloaded Ruby 1.9.2 and the dev kit. I've downloaded the gitbook and its files <a href="https://github.com/schacon/gitbook" rel="nofollow">.gitbook</a></p> <p>I'm now at the situation where it tells me it can't find the script files, and after trying updating the windows Path variable, and moving the .gitbook folder to various locations I still can't make any progress..</p> <p>The trace option gave the following (sorry it doesn't format properly!). It still looks like some silly path error but help is needed...</p> <pre><code>D:\Ruby192\bin\gitbook&gt;rake html --trace (in D:/Ruby192/bin/gitbook) rake aborted! no such file to load -- script/merge &lt;internal:lib/rubygems/custom_require&gt;:29:in `require' &lt;internal:lib/rubygems/custom_require&gt;:29:in `require' D:/Ruby192/bin/gitbook/Rakefile:1:in `&lt;top (required)&gt;' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `load' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2017:in `block in load_rakefile' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2000:in `block in run' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1998:in `run' D:/Ruby192/lib/ruby/gems/1.9.1/gems/rake-0.8.7/bin/rake:31:in `&lt;top (required)&gt;' D:/Ruby192/bin/rake:19:in `load' D:/Ruby192/bin/rake:19:in `&lt;main&gt;' </code></pre> <p>Any advice welcome.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload