git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Dakota Hawkins" <dakotahawkins@gmail.com>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Michael J Gruber" <git@drmicha.warpmail.net>,
	"Duy Nguyen" <pclouds@gmail.com>,
	"git-for-windows" <git-for-windows@googlegroups.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Git for Windows documentation, was Re: [git-for-windows] Re: [ANNOUNCE] Git for Windows 2.9.3
Date: Thu, 25 Aug 2016 00:28:14 +0100	[thread overview]
Message-ID: <99BC268995014F88A25852349769FD02@PhilipOakley> (raw)
In-Reply-To: CAG0BQXmovWAjn8sE=CFGMXguRpEqU3xUbF03aSEN4OLxNc9oZg@mail.gmail.com

From: "Dakota Hawkins" <dakotahawkins@gmail.com>
> 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


  reply	other threads:[~2016-08-24 23:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13 10:14 [ANNOUNCE] Git for Windows 2.9.3 Johannes Schindelin
2016-08-13 15:50 ` Junio C Hamano
2016-08-17 13:54   ` Johannes Schindelin
2016-08-17 15:29     ` Junio C Hamano
2016-08-18  8:37       ` Johannes Schindelin
2016-08-22 14:04         ` [git-for-windows] " Duy Nguyen
2016-08-23 13:54           ` Johannes Schindelin
2016-08-23 14:41             ` Michael J Gruber
2016-08-23 15:37               ` Johannes Schindelin
2016-08-23 16:05                 ` Johannes Schindelin
2016-08-23 19:25                   ` Junio C Hamano
2016-08-23 21:42                     ` Junio C Hamano
2016-08-24  1:04                       ` Dakota Hawkins
2016-08-24 15:41                         ` Git for Windows documentation, was " Johannes Schindelin
2016-08-24 16:06                           ` Dakota Hawkins
2016-08-24 23:28                             ` Philip Oakley [this message]
2016-08-25 11:42                             ` Johannes Schindelin
2016-08-24 15:39                     ` Johannes Schindelin
2016-08-24  5:09                   ` Junio C Hamano
2016-08-24 15:48                     ` core.autocrlf, was " Johannes Schindelin
2016-08-24 16:45                       ` Junio C Hamano
2016-08-25 11:54                         ` Johannes Schindelin
2016-08-25 12:43                           ` Torsten Bögershausen
2016-08-25 13:50                             ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99BC268995014F88A25852349769FD02@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dakotahawkins@gmail.com \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).