--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To post to this group, send email to rubyin...@googlegroups.com.
To unsubscribe from this group, send email to rubyinstalle...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
To unsubscribe from this group, send email to rubyinstalle...@googlegroups.com.
Thanks, Roy. That helped.
Actually, as a non-initiate, I expected documentation to appear when I
clicked the link in the Start Menu, just as happens when I click on
Ruby 1.9.2-p0 API Reference or The Book of Ruby. The command that is
executed apparently fires up the server(s) but does not then open the
relevant page in the default browser.
What seems to work is to
* first select RubyGems Documentation Server (from the Start Menu);
* then point a browser at http://localhost:8808 (as you advised).
I guess this makes sense if you already know how to do it, but it's
not obvious to someone who is new to Ruby.
On Sat, Dec 4, 2010 at 12:36 AM, mindshadow <cdw...@gmail.com> wrote:Thanks, Roy. That helped.
Actually, as a non-initiate, I expected documentation to appear when I
clicked the link in the Start Menu, just as happens when I click on
Ruby 1.9.2-p0 API Reference or The Book of Ruby. The command that is
executed apparently fires up the server(s) but does not then open the
relevant page in the default browser.
What seems to work is to
* first select RubyGems Documentation Server (from the Start Menu);
* then point a browser at http://localhost:8808 (as you advised).
I guess this makes sense if you already know how to do it, but it's
not obvious to someone who is new to Ruby.
--This is an awesome opportunity to improve the gem server behavior, as RubyGems team is wrapping things for 1.4 release.Would you mind open an Issue for us with your feature suggestion? we can provide the patches to RubyGems in some sort of "--launch" parameter so when the server is started, it fires the browser.Thank you for your feedback.
Luis Lavena
AREA 17
-
I've written up an issue but cannot find any way to add it. The
Issues tab doesn't appear to have an Add button, and the New issue tab
says "No tracker is associated to this project. Please check the
Project settings." Any suggestions?
On the http://www.ruby-lang.org/en/libraries/ page, I found this link
Issue Tracking: Report or help solve issues in Ruby. (http://
redmine.ruby-lang.org/)
From there, I found
http://redmine.ruby-lang.org/wiki/ruby/HowtoReport
http://redmine.ruby-lang.org/projects/ruby/issues
After going to the page you supplied (https://github.com/oneclick/
rubyinstaller/issues)
and signing up, I find a Create Issue button, but when I click that, I
am sent to
https://github.com/
which has nothing to do with creating issues.
--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To post to this group, send email to rubyin...@googlegroups.com.
To unsubscribe from this group, send email to rubyinstalle...@googlegroups.com.
I've forked rubygems on github, and made a gem_server_launch branch
[1]. I have made the necessary changes[2]. I have not tested them on
any other OS than Windows yet. I'd appreciate it if Luis, or anyone
else could review it for me.
[1] https://github.com/vertiginous/rubygems/commits/gem_server_launch
[2] https://github.com/vertiginous/rubygems/commit/28822b581aa5645d7dd6247bd5e49c72c389635f
I've forked rubygems on github, and made a gem_server_launch branch
[1]. I have made the necessary changes[2]. I have not tested them on
any other OS than Windows yet. I'd appreciate it if Luis, or anyone
else could review it for me.
[1] https://github.com/vertiginous/rubygems/commits/gem_server_launch
[2] https://github.com/vertiginous/rubygems/commit/28822b581aa5645d7dd6247bd5e49c72c389635f
Good idea, Luis. I've updated it per your suggestion [1]. If the
user provides a command with --launch=command , the command will be
used to attempt to open the browser. If no command is given (ie.
--launch), it will default to 'start' on Windows, and 'open'
everywhere else.
This should probably be documented somewhere, but I'm not sure the
best place. Perhaps in Gem::Commands::ServerCommand#description ?
Gordon
[1] https://github.com/vertiginous/rubygems/commit/585ee90fa289baee2e58c0ff897570c4fb4a0b67
Good idea, Luis. I've updated it per your suggestion [1]. If the
user provides a command with --launch=command , the command will be
used to attempt to open the browser. If no command is given (ie.
--launch), it will default to 'start' on Windows, and 'open'
everywhere else.
This should probably be documented somewhere, but I'm not sure the
best place. Perhaps in Gem::Commands::ServerCommand#description ?
Pull request sent. I also created a rubyinstaller branch to add the
--launch switch to the Rubygems Documentation Server icon.