RFC: Rename --gfm to --comments

[joeyespo]

There's been a few issues caused by the confusion of what --gfm does:

• gfm: headers with no space after hash #63
• Tell the gh api to enable anchors for --gfm #115 (on Twitter)
• Anchor Tags not properly being rendered. #137 (comment)

I also see --gfm being used in a lot of --export examples. I wonder if that's the intention, or if people saw "--gfm" and thought "oh, GitHub Flavored Markdown, that's what I want":

• Error on Windows: could not retrieve styles #89 (comment)
• TypeError: Can't use a string pattern on a bytes-like object #100 (comment)
• Support for Tables Using GFM #102
• Export feature not working in Python 3.4.3 #129 (comment)

As a reminder, --gfm comes directly from the GitHub API, but that doesn't mean we can't use a more meaningful name in Grip.

I'm thinking of renaming it to --comments, since that removes any ambiguity of what it's rendering. --issues is another suggestion (or as an alias), but in a way, all issues are comments, so I think using the more general name will be clear enough. It'll certainly be more clear than --gfm.

Thoughts from anyone here?

[joeyespo]

Renamed to --user-content in #150. The name comes from the GitHub API docs.

[clawoflight]

Yeah, that will clear up a lot of confusion :)