Anatomy of a shell command

[weaverbel]

Suggestions from Jamie @jamieviva that we add something on the general structure of bash. So, something like:

COMMAND -FLAG FILE.USED

Then explain structure of what happens thereafter, so:

if you add nothing = print to shell; if you add > FILE.OUTPUT = save to file; if you add '|' = save to memory for next command.

It probably should do somewhere in https://github.com/data-lessons/library-shell/blob/gh-pages/_episodes/01-intro-shell.md not before doing work in the shell, but as a "look at what you've also learned!" outcome.

Thoughts?

More: https://github.com/data-lessons/library-shell-DEPRECATED/issues/28

[libcce]

@jt14den @dakane1 @annaoates looks like we never got around to this issue. I found https://softcover.s3.amazonaws.com/636/learn_enough_command_line/images/figures/anatomy.png as an example. We can consider a callout after the introduction here https://librarycarpentry.org/lc-shell/01-intro-shell/index.html like:

prompt$ command -option argument.txt

with some text to explain what each part is?

Also, why do we have a note to the instructor on that page? Should we remove the note?