New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce Man pages #698

Open
bboucek opened this Issue Jan 31, 2018 · 3 comments

Comments

Projects
None yet
5 participants
@bboucek

bboucek commented Jan 31, 2018

There should be an introduction to man pages for shell-novice at the beginning of the lesson.

@colinmorris

This comment has been minimized.

Contributor

colinmorris commented Feb 1, 2018

Currently, man is introduced about halfway through episode 02. This is right after we introduce ls, which is the first command they'll run that has any interesting options.

Is there a specific earlier point you'd suggest moving it to?

@bagustris

This comment has been minimized.

Contributor

bagustris commented Mar 8, 2018

I would like to suggest to link one of the word man in that episode 02 to this wikipedia link. It also important to give learner motivation that almost (80%) of Unix shell coding problem can be solved by only reads the man page [1].

I found the shell-extras gives a more comprehensive reading about man pages. The learner should be directed there if he/she want to learn deeper.

[1] http://www.readthefuckingmanual.com/

@elenavataga

This comment has been minimized.

elenavataga commented Mar 9, 2018

I believe section about navigating man pages would benefit from some extension:

"To navigate through the man pages, you may use the up and down arrow keys to move line-by-line, or try the “b” and spacebar keys to skip up and down by a full page. "

=> "Page up" and "page down" keys work with man pages and it is the most intuitive choice (comparing with "b" and spacebar)

"To search for a character or word in the man pages, use “/” followed by the character or word you are searching for."
What about cases when there are more then single occurrence? It can be misleading when only the first match is visible.
Suggested edit:
=> "To search for a character or word in the man pages, use “/” followed by the character or word you are searching for, press "n" to move to the next occurrence."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment