I vividly remember being extremely frustrated because every forum post on the topic seemed to assume you understood what they were asking you to do.
Man pages can be read by opening a terminal/console window and typing in ‘man [command]’, then pressing enter. Generally you can scroll through them with up/down arrow and pgup/down.
Normally the man page name is the same as the command, so I’m not sure how anyone would discover the one for gittutorial.
Or even your scroll wheel! :D
> Normally the man page name is the same as the command, so I’m not sure how anyone would discover the one for gittutorial.
At the bottom of every man page there is a SEE ALSO section:
SEE ALSO
gittutorial(7), gittutorial-2(7), giteveryday(7), gitcvs-migration(7), gitglossary(7), gitcore-tutorial(7), gitcli(7), The Git User’s Manual[1], gitworkflows(7)
This is as close to clickable links as man gets; if you want actual links you could run “info git” instead. There is also occasionally a NOTES section: NOTES
1. Git User’s Manual
file:///usr/share/doc/git/user-manual.html
2. Trace2 documentation
file:///usr/share/doc/git/technical/api-trace2.html
3. Git concepts chapter of the user-manual
file:///usr/share/doc/git/user-manual.html#git-concepts
4. howto
file:///usr/share/doc/git/howto-index.html
5. Git API documentation
file:///usr/share/doc/git/technical/api-index.html
It also happens to mention gittutorial(7) and giteveryday(7) in the second sentence of the description, way back at the top of the man page. These are above the fold even in an 80×24 terminal.1. Have some unix-like operating system. 2. Type `man` at a command prompt.
Is that about right? I haven't got to step 1 yet.
But even if you cannot (for some unfathomable reason) git has you covered. You can type “git help foo” to open git’s man page for foo. So “git help tutorial” or “git help gittutorial” will both work.
Man pages are something that UNIX really did right. When you bought a UNIX, it came with many volumes of printed reference materials covering every detail. Every command you could type, every C library function you could call, every syscall, was documented right there in the manual on your shelf.
But they went one step further and provided the source for those manuals on the computer itself (literally, they were printed from the same troff files that the man viewer displays to you), so that you could view anything in those manuals without even taking them down off of your shelf. They’re indexed for instant retrieval and fast searches, so that there’s literally no delay when you ask for help. And they’re usually really high quality too! Sometimes they delve into jargon, or fail to spell out all of the consequences of some obscure option, but it is super rare that they leave anything out. Originally they were maintained by professional documentation writers, but these days they are lovingly maintained by volunteers who spend thousands of hours keeping them up to date.
There’s a whole education’s worth of material in there, and people just don’t use them. I can only blame learned helplessness, or Windows.
I bet you don’t know about Info either.
PS C:\> git --version
git version 2.32.0.windows.2
PS C:\> man git
Get-Help : Get-Help could not find git in a help file in this session. To download updated help topics type:
"Update-Help". To get help online, search for the help topic in the TechNet library at
https:/go.microsoft.com/fwlink/?LinkID=107116.
I use `git help` regularly. I always pass it a git command. I didn't know there were other topics you can pass.I do know about "Info", in several contexts. Foremost, it's short for "information". But I bet that's not what you're talking about. Trying to run it yields "info : The term 'info' is not recognized as..." and so on.
That makes me even sadder. They apparently don’t have man pages. :(
Have you ever used the SEE ALSO section in the git man pages to find related information? Could you have missed the links to non–commands merely because you already knew some git commands, so you never ran “git help” without one and thus you never saw the links to the tutorial? Or is there some other cause?
Incidentally, info is a different way to read documentation, one incorporating hyperlinks and a much more book–like organizational system of chapters, sections, etc. It’s a better way to document really large programs like Emacs. It’s available on most OSes, except apparently yours, and like man it allows applications to install their own documentation. It can also read man pages; it doesn’t change them very much (they don’t have chapters, for example), but it does turn references to other man pages into actual links.