git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git for Windows documentation, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3

From
Philip Oakley <philipoakley@iee.org>
Date
Aug 24, 2016, 23:28 UTC
Message-ID
<99BC268995014F88A25852349769FD02@PhilipOakley>
In-Reply-To
<CAG0BQXmovWAjn8sE=CFGMXguRpEqU3xUbF03aSEN4OLxNc9oZg@mail.gmail.com>
From: "Dakota Hawkins" <dakotahawkins@gmail.com>
Show 31 quoted lines
> On Wed, Aug 24, 2016 at 11:41 AM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> Hi Dakota,
>>
>> On Tue, 23 Aug 2016, Dakota Hawkins wrote:
>>
>>> I use GFW almost exclusively, but I pretty much always consult the
>>> upstream documentation anyway (because I find it easier).
>>
>> Oh... I thought that typing "git help git-commit" opening a nice HTML 
>> page
>> in your favorite browser was good enough.
>>
>> Do you have any suggestion how to improve the user experience?
>
> Just a small one, and that's that I'd prefer the option to have help
> display in my terminal (that option might exist and I don't know how
> to turn it on). That would be very convenient for me.
>
> Opening a nice HTML page is probably nice for a lot of users. What
> frustrates me about it is that I don't know which browser window on
> which monitor (of 3) it's going to open in, so it's a context-switch
> to a different window somewhere that I don't have much control over.
>
> The thing I find easier about using the upstream documentation is just
> that I can pick the browser window I want it to come up in, and it's
> usually faster enough for me to just google "git-whatever" or
> re-purpose an open doc tab. I don't prefer the _content_ of the
> upstream documentation, it's just less frustrating for me to use, if
> that makes sense.
>

If you would like to use the man pages, then one option is to install the SDK, which then allows you to install the man package, (setting the manpath as required) to allow your choice of viewer. You may need to set the minnty config BoldAsFont=yes if you want the bold for the headings in the man pages.

With the SDK you can also create a personal release version of GfW that includes the man viewer if you like. -- Philip

Previous: Dakota HawkinsNext: Johannes Schindelin
Message 16 of 24 in “[ANNOUNCE] Git for Windows 2.9.3”
  1. Johannes SchindelinAug 13, 2016
  2. Junio C HamanoAug 13, 2016
  3. Johannes SchindelinAug 17, 2016
  4. Junio C HamanoAug 17, 2016
  5. Johannes SchindelinAug 18, 2016
  6. Duy NguyenAug 22, 2016
  7. Johannes SchindelinAug 23, 2016
  8. Michael J GruberAug 23, 2016
  9. Johannes SchindelinAug 23, 2016
  10. Johannes SchindelinAug 23, 2016
  11. Junio C HamanoAug 23, 2016
  12. Junio C HamanoAug 23, 2016
  13. Dakota HawkinsAug 24, 2016
  14. Git for Windows documentation, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3Johannes Schindelin, Aug 24, 2016
  15. Dakota HawkinsAug 24, 2016
  16. Philip OakleyAug 24, 2016
  17. Johannes SchindelinAug 25, 2016
  18. Johannes SchindelinAug 24, 2016
  19. Junio C HamanoAug 24, 2016
  20. core.autocrlf, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3Johannes Schindelin, Aug 24, 2016
  21. Junio C HamanoAug 24, 2016
  22. Johannes SchindelinAug 25, 2016
  23. Torsten BögershausenAug 25, 2016
  24. Johannes SchindelinAug 25, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.