Suggestion

[MtnBiker]

Great little gem.

I've just tried it, but would whatthegem <gem> displaying all the pieces of information be easier to use, and if you only want a specific piece then add stats, info, etc.

[zverok]

Thanks! I thought about it (well, not exactly, but I initially imagined whatthegem <gem> all to output everything), but after some experimenting, I've decided against it. The reason is: most of the time, different commands are necessary in different contexts, so I've just added a brief info header of top of all the commands (initially it wasn't there). Only info and stats contexts are somewhat intersecting (and they probably are good candidates for merge): "what is it, generally?" + "how maintained/popular is it?" But typically when you asking that ↑ question, you don't want to see 3 screens of the changelog. And when you are asking for a changelog (oh, the gem was updated, sooo what exactly changed?), you don't need usage, and vice versa. And both usage and changelog could be rather long (especially changelog, but typical "good" usage is also a screen or more, at least on my 13" laptop), so I can't imagine a lot of situations when you'll be happy with 5-7 screens of "everything you can get". So the default (info) would stay short, at least for now.

(Another factor is how long the command performs -- for example, stats is not merged into info because it makes several requests to different APIs, so it would make "default" command performing several more seconds, which is not always desirable.)