Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Proposal about --help options and man calls
Date: Wed, 18 Jul 2007 16:16:41 -0700	[thread overview]
Message-ID: <7v644h715y.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <85y7hdwfds.fsf@lola.goethe.zz> (David Kastrup's message of "Wed, 18 Jul 2007 23:50:23 +0200")

David Kastrup <dak@gnu.org> writes:

> Frequently, git somecommand --help will call the man command to
> display help pages.  I think that when it does so, it should pass the
> value of the GIT_PAGER variable copied into the PAGER variable: the
> paging happens on behalf of git here.

Hmph.  Is that to help people who uses GIT_PAGER but no PAGER,
or have both but set it differently (setting both and in the
same way does not make much sense).  But what it means is that
"git command --help" and "man git-command" would be paged
differently.  I highly doubt it is really desirable.

What's the reason to set GIT_PAGER and PAGER differently to
begin with?  Can people give examples of the reason why?

By the way, I would understand if there is a request to honor
GIT_LESS environment and if it exists export its value instead
of FRSX as LESS when we spawn the pager.  As some people do not
want S nor R for other programs but do want them for colored git
output that tends to consist of long lines.  This is a slightly
related topic, but different from the issue you raised in your
message.

  reply	other threads:[~2007-07-18 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 21:50 Proposal about --help options and man calls David Kastrup
2007-07-18 23:16 ` Junio C Hamano [this message]
2007-07-18 23:28   ` David Kastrup
2007-07-19 10:42     ` Steven Grimm
2007-07-19  3:49   ` Brian Gernhardt

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

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

  git send-email \
    --in-reply-to=7v644h715y.fsf@assigned-by-dhcp.cox.net \
    --to=gitster@pobox.com \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox