From: Junio C Hamano <gitster@pobox.com>
To: Sergei Organov <osv@javad.com>
Cc: "Aneesh Kumar" <aneesh.kumar@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git help error
Date: Tue, 04 Dec 2007 11:40:15 -0800 [thread overview]
Message-ID: <7vr6i245b4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <874pey9uow.fsf@osv.gnss.ru> (Sergei Organov's message of "Tue, 04 Dec 2007 21:33:03 +0300")
Sergei Organov <osv@javad.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>> "Aneesh Kumar" <aneesh.kumar@gmail.com> writes:
>>
>>> git help gives me the below error.
>>>
>>> [master@git]$ git help add
>>> No manual entry for git-add
>>> See 'man 7 undocumented' for help when manual pages are not available.
>>> [master@git]$
>>>
>>> I have the git binaries installed via --prefix
>>>
>>> ./configure --prefix=/home/kvaneesh/bin-local/git/
>>> and to see the man page i have to say
>>>
>>> man -M /home/kvaneesh/bin-local/git/share/man/
>> ...
>> When you run "man" from the command line, can you say
>>
>> $ man git-add
>>
>> and make it work? If it fails the same way, then what you are missing
>> is MANPATH environment variable, isn't it?
>
> I think what the OP asked for makes sense. git-help should better find
> corresponding version of manual pages automatically. This way, if one
> invokes different versions of git-help, he will get corresponding
> version of help text.
I do not necessarily agree. Read what Aneesh wrote originally again,
and read what he _didn't_ write.
Not only he needs to run his "man" with -M (and my point was that it is
not the only way, by the way), he needs to futz with his $PATH to
include $HOME/bin-local/git for _his_ installation to work.
I think my suggestion to use $MANPATH is in line with what he is already
doing. If you install things in non-standard places, you can use
environments to adjust to what you did, and that's the reason PATH and
MANPATH environments are supported by your tools.
Having said that, I do not mind accepting a patch that prepends the
nonlocal path to MANPATH in help.c::show_man_page().
next prev parent reply other threads:[~2007-12-04 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 16:26 git help error Aneesh Kumar
2007-12-04 17:55 ` Junio C Hamano
2007-12-04 18:33 ` Sergei Organov
2007-12-04 19:40 ` Junio C Hamano [this message]
2007-12-04 19:47 ` Luciano Rocha
2007-12-04 19:50 ` David Kastrup
2007-12-04 20:06 ` Luciano Rocha
2007-12-06 18:36 ` Sergei Organov
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=7vr6i245b4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=osv@javad.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).