Bash prompts and single-word heading capitalization

[RichardLitt]

Waiting for LGTM from:

• @whyrusleeping
• @dignifiedquire
• @rht
• @diasdavid
• @jbenet

[dignifiedquire]

LGTM

[hackergrrl]

What does "bash arguments" mean here? Perhaps "command line invocations"?

[dignifiedquire]

Maybe not bash but rather shell as there are more shells than just bash ;)

[RichardLitt]

shell makes sense. Does that satisfy you, @noffle?

[hackergrrl]

I'm partial to command line, if only because I get the [subjective] impression more people know what it means than shell. Either works for me. 👍

[rht]

('shell' includes graphical as well as voice input, e.g. https://www.emacswiki.org/emacs/EmacSpeak)

[rht]

Citation suggestion: much like how https://github.com/ipfs/community/blob/master/code-of-conduct.md attributes the npm code of conduct, I think this should be the case as well for docs-styleguide.md.
http://man7.org/linux/man-pages/man7/man-pages.7.html should be cited (better if there is an immutable link to this).

('@'related: if you want to see what precedes npm coc, and so on, here is an incomplete visualization of it http://ideapad.io/code-of-conduct-phylogenetic-tree/graph)

[daviddias]

LGTM

[RichardLitt]

@rht That makes sense to me. We can link that. Want to make a PR about it?

[dignifiedquire]

Ping @whyrusleeping @rht @jbenet for review

[whyrusleeping]

@jbenet is going to want > instead of $ i think, i saw him post about that recently

[RichardLitt]

@whyrusleeping agreed. I'm not sure when to use that: everywhere?

I see two issues with this. One is that most beginners come from Mac environments, I would think, and would be used to $. The second is that I have often seen this notation:

$ run command
> this is the output

Where > is used to mean STDOUT. I wonder if > would lead people to wonder if it is STDOUT or the command.

[whyrusleeping]

yeah, i'm personally not a fan of using > and prefer $. this PR has a LGTM from me

[dignifiedquire]

I just checked man git-commit and it does

It is a rough equivalent for:

$ git reset --soft HEAD^
$ ... do something else to come up with the right tree ...
$ git commit -c ORIG_HEAD