What's the point of using `brew man` to install man pages as markdown and how do I uninstall everything it downloaded?


#1

The man pages render just fine in terminal, why would I want them stored in a separate file?

It downloads 3 gems (and doesn’t specify where they’re installed) the first time I run it but when I brew untap homebrew/bundle and then brew man again, it skips the download and goes straight to tapping. And md file wasn’t removed after untapping.

brew help man or brew man --help don’t return anything interesting.

$ brew man
==> Installing or updating 'ronn' gem
Building native extensions.  This could take a while...
Successfully installed rdiscount-2.2.0.1
Fetching: hpricot-0.8.6.gem (100%)
Building native extensions.  This could take a while...
Successfully installed hpricot-0.8.6
Fetching: ronn-0.7.3.gem (100%)
Successfully installed ronn-0.7.3
3 gems installed
==> Tapping homebrew/bundle
Cloning into '/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle'...
remote: Counting objects: 64, done.
remote: Compressing objects: 100% (57/57), done.
remote: Total 64 (delta 5), reused 36 (delta 4), pack-reused 0
Unpacking objects: 100% (64/64), done.
Tapped 1 command (140 files, 193.4KB).
Writing markdown to /usr/local/Homebrew/docs/Manpage.md
Writing man page to /usr/local/Homebrew/manpages/brew.1
Writing man page to /usr/local/Homebrew/manpages/brew-cask.1
No changes to manpage output detected.

(Mike McQuaid) #2

brew man --help: Generate Homebrew's manpages.. This is used for developers to generate the manpages. You don’t need to run this command unless you submit a pull request to change them. The manpages are displayed in a .1 file but generated from a .md file.


#3

Ah I see, thanks Mike!

Might be useful to add something in “help” explaining that it’s for development.

Additionally I wish the install output said where the gems are being installed, as mentioned previously.