On 21/05/2020 00:56, Junio C Hamano wrote: > Philip Oakley <philipoakley@iee.email> writes: > >> Hi Junio, >> >> On 20/05/2020 22:27, Junio C Hamano wrote: >>> Philip Oakley <philipoakley@iee.email> writes: >>> >>>> I can then browse that directory to find user-manual.html and open it >>>> from there (because I know it is there!). >>>> >>>> How do Git on Linux users launch/read the user-manual? >>> Start from the same starting point >>> >>> $ git help -w git >>> >>> and then navigate to the link to "Git User Manual"? >>> >> And then what? Is it always some .html viewer, or viewing the raw .txt >> file, or something else? (it isn't the man view..) > "git help -w" is showing stuff in the web browser, and when you open > git(1), which is rendered in HTML, and visit "Git User's Manual" > link in it, the experience would be no different from those viewing > via the browser on Windows---$(htmldir)/user-manual.html is where > the rendered HTML version of the user-manual is. > > Or are you asking something else? > I was more coming at the question from the other direction, that is, about accessing, normally, the git manuals, and discovering the desired information, both for existing and new users. In your example, you needed to include the extra -w option, specific to this 'special' manual, while all the other hundreds of man pages would be accessed without it (even on Windows, as the config is set by default). I also get the impression that many linux users may be using 'man' just as much as much as 'git help' but neither (without realising the need for the extra option) would show the user-manual (.txt|.html). We do have the advised `git help -g` to list the concept guides, but that doesn't advise about the user-manual, which surely we should mention to those asking for help (without them needing a long journey of discovery). The list does include `git everyday`... I appreciate that, for some, there is a view that new users are other peoples problems and that knowledgable users already know, roughly, which command they wish to use and thus then peruse the appropriate reference manual to confirm the correct form for their command. I'd rather we direct uncertain users to their appropriate guide quickly, using their expected viewer method. Hence the question. Philip
