From: Jon Seymour <jon.seymour@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add --info-path and --man-path options to git.
Date: Mon, 2 May 2011 10:06:40 +1000 [thread overview]
Message-ID: <BANLkTik-8WVsw-_P7=-pEiXFLeoQQRAVeg@mail.gmail.com> (raw)
In-Reply-To: <7v62puq8a5.fsf@alter.siamese.dyndns.org>
On Mon, May 2, 2011 at 10:02 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>> By contrast, man and info typically use standard search mechanisms:
>> man using $MANPATH and info using the dir.info file. The usual
>> interface to git's documentation through a man browser is not
>>
>> man /usr/share/man/man1/git-add.1.gz
>>
>> but
>>
>> man git-add; # or "man git add" if your man viewer supports it
>
> I think you are forgetting the case where the git-man-path the user uses
> to install git may be outside /usr/share/man (e.g. $HOME/share/man). In
> such an installation, by setting $PATH to include your installed git
> binary (e.g. $HOME/bin), you should be able to say "git help -m git" to
> tell help.c to internally prepend $HOME/share/man to the $MANPATH before
> it kicks "man". Does "man git-add" work without you knowing where that
> directory is (iow, without having $HOME/share/man on $MANPATH)? And if it
> does not, how would you learn what directory to add to your $MANPATH?
>
> Isn't that what this patch is solving? I am not sure where the similarity
> with the html documentation breaks donw. The same thing for info.
Good point. For non-distro installed installations of git, this would
be handy, even for read-only purposes.
jon.
next prev parent reply other threads:[~2011-05-02 0:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 8:16 [PATCH] Add --info-path and --man-path options to git Jon Seymour
2011-05-01 18:15 ` Junio C Hamano
2011-05-01 22:47 ` Jon Seymour
2011-05-01 23:48 ` Jonathan Nieder
2011-05-01 23:53 ` Jonathan Nieder
2011-05-02 0:02 ` Junio C Hamano
2011-05-02 0:06 ` Jon Seymour [this message]
2011-05-02 0:12 ` Jon Seymour
2011-05-02 0:25 ` Jonathan Nieder
2011-05-02 3:47 ` Junio C Hamano
2011-05-02 5:15 ` Jonathan Nieder
2011-05-02 6:07 ` [PATCH] Documentation: clarify meaning of --html-path, --man-path, and --info-path Jonathan Nieder
2011-05-02 6:49 ` Jon Seymour
2011-05-02 17:24 ` Junio C Hamano
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='BANLkTik-8WVsw-_P7=-pEiXFLeoQQRAVeg@mail.gmail.com' \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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.
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 NNTP newsgroup(s).