From: Nick Klauer <klauer@...>
Date: 2011-03-27T21:59:55+09:00
Subject: Re: gem list --remote --details gives "ERROR: While executing gem ... (NoMethodError)"

--0016e6d976512231c0049f7667f4
Content-Type: text/plain; charset=UTF-8

Apologies for sounding snarky.  I didn't intend to.  Don't forget that gem
search is a way to search gem listings as well (and saves you typing the
pipe to grep)

gem search -r <gemName>

And if you want some more details besides just --details,

gem spec -r <gemName>

but I'd lean on those other sites (especially Ruby Toolbox, that site
rocks).  There's also podcasts that try to round up the latest goings-on in
the Ruby community:


   - Ruby5 - http://ruby5.envylabs.com/
   - Ruby Show - http://rubyshow.com/



-Nick Klauer


On Sun, Mar 27, 2011 at 07:39, Markus Fischer <markus@fischer.name> wrote:

> Hi,
>
> On 27.03.2011 13:50, Nick Klauer wrote:
> > I guess we should bring this conversation back around to the heart of the
> > matter: what is it that you want to accomplish by listing all 22,000+
> gems
> > on your local machine?
> >
> > I mean, there are search engines devoted specifically to listing out gems
> > for you (http://www.gemcutter.org, http://www.rubydoc.info/) and giving
> you
> > some pertinent details about the gem itself (such as where to go for more
> > information).  There are resources to help you find the best gem for the
> > task at hand (http://ruby-toolbox.com/), and plenty of other places to
> find
> > out about gems.
>
> indeed .. I didn't realize this, seriously. Whenever I used a ruby
> software before, which required a certain gem, not every software
> clearly says "use this or that gem", I mostly used "gem list --remote| |
> grep name" to figure the right one. I use this because the default
> pattern you can pass to gem only checks for gems beginning with that
> name ... There are other such inconveniences, like "gem help" telling me
> I need "gem help commands" to see all of them. I'd expect "gem help" or
> "gem --help" telling my that. I there weren't the examples, "gem help"
> by itself would only be another help pointer .. not that helpful :/
>
> Now I thought, before installing the gem and I located it already with
> the above grep command, I wanted to have more details. So since I cannot
> pass a pattern to gem which matches anywhere in it's name, only from the
> beginning, I thought I just fetch all of it.
>
> Didn't realize there where sooooo many. I didn't knew all the links you
> posted (especially gemcuttter.org and ruby-toolbox), for me it was just
> the "gem" tool available and I thought I'd use it more or less like I
> use e.g. aptitude/dpkg/apt-cache search and friends (where I seldom
> visited the Debian project web page). It seems it doesn't maintain a
> local package cache dir from the remote site(s?).
>
> As it stands now, it's just a matter for me to realize what "gem" and
> it's objective is and what it isn't. Guess that has been cleared up for
> some points ;-)
>
> thanks,
> - Markus
>
>

--0016e6d976512231c0049f7667f4--