Man what
ozmm.org
ozmm.org
And I agree wholeheartedly.
EDIT: For example:
% gem list | wc -l
89
% gem man --all | tail -n +3 | awk '{ print $1 }' | sort | uniq | wc -l
2
Many gems are libraries rather than binaries/applications, and as such they don't have user-friendly man pages, but they do have documentation in the form of rdoc/yard/what-have-you. On my system, only gem-man and ronn have manpages, but many other gems have documentation via ri - it's just documentation aimed at other programmers rather than end users. For a library, that makes sense to me.
Having said that, it would be nice if Ruby gem authors got into the habit of using ronn and gem-man in the way that Perl CPAN authors use POD.
Also, and this is just nitpicky, but your second command shouldn't need awk, sort or uniq:
gem man --all | tail -n +3 | wc -lIn particular, I'm thinking of things like rails, rspec, heroku, and the like, which, while primarily libraries, have cli components that badly need man pages. I can't tell you how many babies I've punched as a result of typing "man rails" or "man spec". It might be just me, but if it can be the first token in a shell command, I expect it to have a manpage, and it is almost (physically) shocking when that is not true.
(I do need that awk | sort | uniq, because I have multiple versions of unicorn that all show up with that command)
I think it's probably 20% newest programmers are getting less and less interested in the command-line, 20% article is ridiculous and 60% dude was bored wanted to write an easy and thorough article on a programming topic.
(Disclosure: I'm a 40-something who was introduced to man in freshman year classes in the 80's.)
Also, because I didn't know about the cheatsheet project.
It's easy to posture and and use snark to deride someone for saying something you already know. But I think gentle reminders that our systems are discoverable is a good one. I'm currently TAing a Computer Systems course, and that's a key point I want our students to realize.
It's fantastic that you're very comfortable with Unix-based operating systems! Unfortunately, there are lots of people that aren't. There was a time when you weren't.
This is probably the most straightforward explanation of man that I've ever seen, and I have bookmarked it in order to pass it on when I encounter people who would benefit. I don't know about you, but I really enjoy helping people out who are struggling to learn something new.
I hope someday we can get past Unix "RTFM" culture.
there certainly was. but i didn't and i don't expect to learn that kind of thing here.
Ruby itself has ri and rdoc as man alternatives.
I think the point was that man is a widely accepted "unix way" of doing documentation. Just as Unicorn uses unix sockets to great effect, maybe we should focus on writing good manpages instead of reinventing documentation systems over and over again.
That doesn't mean cheat, ri, rdoc aren't better in various ways, just that publishing documentation via the man standard is a nice way to maintain standardized docs.
Hmm. If I release a project, node.hs, can I also name my man page 'node'? What happens if there is a collision?
Are there rules of etiquette when deciding what to call you man pages entry? I.e., what it not have been better for node.js to have it's entry be 'nodejs' or 'node.js'?
my-macbook:~ user$ man up
No manual entry for up
my-macbook:~ user$