Open a library file you can require in your editor. That's it.
gem edit active_support/all
gem edit rake/task thor/task
gem edit -e mvim fileutils
Actually that's not it. You can also open a gem by name.
Your editor's current working directory will be the root of the gem.
I almost forgot. You can also clone a gem from GitHub.
gem clone rails
gem clone -d ~/src capybara
And you can tell it to open the gem in your editor afterwards.
gem clone -o rack
gem clone -oe mvim -d /tmp gem-browse
This one doesn't work if the neither the homepage nor the source code URL point back at GitHub.
That's really it. I mean other than the command that lets you open a gem's homepage in your browser. You know, the command this gem is named after.
RubyGems 1.8 is required to use gem edit, but the other commands will work on any version that supports RubyGems plugins.
If you're using RVM, you can put it in the global gemset (relax, it has no dependencies):
echo gem-browse >> ~/.rvm/gemsets/global.gems
rvm @global do gem install gem-browse
Protip: Install gem-ctags to automatically invoke Ctags on gems as they are installed.
Don't submit a pull request with an ugly commit message or I will ignore your patch until I have the energy to politely explain my zero tolerance policy.
Copyright (c) Tim Pope. MIT License.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4