{"thread":{"id":"11130","subject":"git help error","startedAt":"2007-12-04T16:26:48Z","lastAt":"2007-12-06T18:36:01Z","messageCount":8,"participants":["Aneesh Kumar","Junio C Hamano","Sergei Organov","Luciano Rocha","David Kastrup"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"61924","messageId":"cc723f590712040826o7ca36bfg35b8cb4d64ee8d2d@mail.gmail.com","threadId":"11130","inReplyTo":null,"subject":"git help error","fromName":"Aneesh Kumar","fromEmail":"aneesh.kumar@gmail.com","sentAt":"2007-12-04T16:26:48Z","receivedAt":"2007-12-04T16:26:48Z","isPatch":false,"sender":{"key":"aneesh.kumar@gmail.com","avatar":"https://gravatar.com/avatar/0621fc0b2f14ead1e9024382f16053a808c148596da30c1b92572fa075621f68?d=mp&s=160"},"body":"git help gives me the below error.\n\n[master@git]$ git help add\nNo manual entry for git-add\nSee 'man 7 undocumented' for help when manual pages are not available.\n[master@git]$\n\nI have the git binaries installed via --prefix\n\n./configure --prefix=/home/kvaneesh/bin-local/git/\nand to see the man page i have to say\n\nman -M /home/kvaneesh/bin-local/git/share/man/\n\nI guess git-help need to take care of the prefix.\n\n-aneesh\n"},{"id":"61930","messageId":"7v1wa25oqc.fsf@gitster.siamese.dyndns.org","threadId":"11130","inReplyTo":"cc723f590712040826o7ca36bfg35b8cb4d64ee8d2d@mail.gmail.com","subject":"Re: git help error","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-12-04T17:55:23Z","receivedAt":"2007-12-04T17:55:23Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Aneesh Kumar\" writes:\n\n> git help gives me the below error.\n>\n> [master@git]$ git help add\n> No manual entry for git-add\n> See 'man 7 undocumented' for help when manual pages are not available.\n> [master@git]$\n>\n> I have the git binaries installed via --prefix\n>\n> ./configure --prefix=/home/kvaneesh/bin-local/git/\n> and to see the man page i have to say\n>\n> man -M /home/kvaneesh/bin-local/git/share/man/\n>\n> I guess git-help need to take care of the prefix.\n\nWhen you run \"man\" from the command line, can you say\n\n $ man git-add\n\nand make it work? If it fails the same way, then what you are missing\nis MANPATH environment variable, isn't it?\n"},{"id":"61934","messageId":"874pey9uow.fsf@osv.gnss.ru","threadId":"11130","inReplyTo":"7v1wa25oqc.fsf@gitster.siamese.dyndns.org","subject":"Re: git help error","fromName":"Sergei Organov","fromEmail":"osv@javad.com","sentAt":"2007-12-04T18:33:03Z","receivedAt":"2007-12-04T18:33:03Z","isPatch":false,"sender":{"key":"osv@javad.com","avatar":null},"body":"Junio C Hamano writes:\n> \"Aneesh Kumar\" writes:\n>\n>> git help gives me the below error.\n>>\n>> [master@git]$ git help add\n>> No manual entry for git-add\n>> See 'man 7 undocumented' for help when manual pages are not available.\n>> [master@git]$\n>>\n>> I have the git binaries installed via --prefix\n>>\n>> ./configure --prefix=/home/kvaneesh/bin-local/git/\n>> and to see the man page i have to say\n>>\n>> man -M /home/kvaneesh/bin-local/git/share/man/\n>>\n>> I guess git-help need to take care of the prefix.\n>\n> When you run \"man\" from the command line, can you say\n>\n> $ man git-add\n>\n> and make it work? If it fails the same way, then what you are missing\n> is MANPATH environment variable, isn't it?\n\nI think what the OP asked for makes sense. git-help should better find\ncorresponding version of manual pages automatically. This way, if one\ninvokes different versions of git-help, he will get corresponding\nversion of help text.\n\n-- \nSergei.\n"},{"id":"61936","messageId":"7vr6i245b4.fsf@gitster.siamese.dyndns.org","threadId":"11130","inReplyTo":"874pey9uow.fsf@osv.gnss.ru","subject":"Re: git help error","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-12-04T19:40:15Z","receivedAt":"2007-12-04T19:40:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sergei Organov writes:\n\n> Junio C Hamano writes:\n>> \"Aneesh Kumar\" writes:\n>>\n>>> git help gives me the below error.\n>>>\n>>> [master@git]$ git help add\n>>> No manual entry for git-add\n>>> See 'man 7 undocumented' for help when manual pages are not available.\n>>> [master@git]$\n>>>\n>>> I have the git binaries installed via --prefix\n>>>\n>>> ./configure --prefix=/home/kvaneesh/bin-local/git/\n>>> and to see the man page i have to say\n>>>\n>>> man -M /home/kvaneesh/bin-local/git/share/man/\n>> ...\n>> When you run \"man\" from the command line, can you say\n>>\n>> $ man git-add\n>>\n>> and make it work? If it fails the same way, then what you are missing\n>> is MANPATH environment variable, isn't it?\n>\n> I think what the OP asked for makes sense. git-help should better find\n> corresponding version of manual pages automatically. This way, if one\n> invokes different versions of git-help, he will get corresponding\n> version of help text.\n\nI do not necessarily agree. Read what Aneesh wrote originally again,\nand read what he _didn't_ write.\n\nNot only he needs to run his \"man\" with -M (and my point was that it is\nnot the only way, by the way), he needs to futz with his $PATH to\ninclude $HOME/bin-local/git for _his_ installation to work.\n\nI think my suggestion to use $MANPATH is in line with what he is already\ndoing. If you install things in non-standard places, you can use\nenvironments to adjust to what you did, and that's the reason PATH and\nMANPATH environments are supported by your tools.\n\nHaving said that, I do not mind accepting a patch that prepends the\nnonlocal path to MANPATH in help.c::show_man_page().\n"},{"id":"61937","messageId":"20071204194754.GB30780@bit.office.eurotux.com","threadId":"11130","inReplyTo":"7vr6i245b4.fsf@gitster.siamese.dyndns.org","subject":"Re: git help error","fromName":"Luciano Rocha","fromEmail":"strange@nsk.no-ip.org","sentAt":"2007-12-04T19:47:54Z","receivedAt":"2007-12-04T19:47:54Z","isPatch":false,"sender":{"key":"strange@nsk.no-ip.org","avatar":null},"body":"On Tue, Dec 04, 2007 at 11:40:15AM -0800, Junio C Hamano wrote:\n> Sergei Organov writes:\n> \n> > Junio C Hamano writes:\n> >> \"Aneesh Kumar\" writes:\n> >>\n> >>> git help gives me the below error.\n> >>>\n> >>> [master@git]$ git help add\n> >>> No manual entry for git-add\n> >>> See 'man 7 undocumented' for help when manual pages are not available.\n> >>> [master@git]$\n> >>>\n> >>> I have the git binaries installed via --prefix\n> >>>\n> >>> ./configure --prefix=/home/kvaneesh/bin-local/git/\n> >>> and to see the man page i have to say\n> >>>\n> >>> man -M /home/kvaneesh/bin-local/git/share/man/\n> >> ...\n> >> When you run \"man\" from the command line, can you say\n> >>\n> >> $ man git-add\n> >>\n> >> and make it work? If it fails the same way, then what you are missing\n> >> is MANPATH environment variable, isn't it?\n> >\n> > I think what the OP asked for makes sense. git-help should better find\n> > corresponding version of manual pages automatically. This way, if one\n> > invokes different versions of git-help, he will get corresponding\n> > version of help text.\n> \n> I do not necessarily agree. Read what Aneesh wrote originally again,\n> and read what he _didn't_ write.\n> \n> Not only he needs to run his \"man\" with -M (and my point was that it is\n> not the only way, by the way), he needs to futz with his $PATH to\n> include $HOME/bin-local/git for _his_ installation to work.\n> \n> I think my suggestion to use $MANPATH is in line with what he is already\n> doing. If you install things in non-standard places, you can use\n> environments to adjust to what you did, and that's the reason PATH and\n> MANPATH environments are supported by your tools.\n> \n> Having said that, I do not mind accepting a patch that prepends the\n> nonlocal path to MANPATH in help.c::show_man_page().\n\nActually, current man utilities locate the manual page by looking where\nthe executable is, if MANPATH isn't defined (tested in Linux and\nDarwin).\n\nSo, \"unset MANPATH; man git-add\" should be sufficient.\n\n-- \nlfr\n0/0\n"},{"id":"61938","messageId":"863auiw86m.fsf@lola.quinscape.zz","threadId":"11130","inReplyTo":"20071204194754.GB30780@bit.office.eurotux.com","subject":"Re: git help error","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2007-12-04T19:50:41Z","receivedAt":"2007-12-04T19:50:41Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"Luciano Rocha writes:\n\n> On Tue, Dec 04, 2007 at 11:40:15AM -0800, Junio C Hamano wrote:\n>\n>> Having said that, I do not mind accepting a patch that prepends the\n>> nonlocal path to MANPATH in help.c::show_man_page().\n>\n> Actually, current man utilities locate the manual page by looking where\n> the executable is, if MANPATH isn't defined (tested in Linux and\n> Darwin).\n>\n> So, \"unset MANPATH; man git-add\" should be sufficient.\n\nThat only works for paths registered in /etc/manpath.config (or an\nequivalent config file depending on system/distribution).\n\n-- \nDavid Kastrup\n"},{"id":"61941","messageId":"20071204200625.GA32717@bit.office.eurotux.com","threadId":"11130","inReplyTo":"863auiw86m.fsf@lola.quinscape.zz","subject":"Re: git help error","fromName":"Luciano Rocha","fromEmail":"luciano@eurotux.com","sentAt":"2007-12-04T20:06:25Z","receivedAt":"2007-12-04T20:06:25Z","isPatch":false,"sender":{"key":"luciano@eurotux.com","avatar":null},"body":"On Tue, Dec 04, 2007 at 08:50:41PM +0100, David Kastrup wrote:\n> Luciano Rocha writes:\n> \n> > On Tue, Dec 04, 2007 at 11:40:15AM -0800, Junio C Hamano wrote:\n> >\n> >> Having said that, I do not mind accepting a patch that prepends the\n> >> nonlocal path to MANPATH in help.c::show_man_page().\n> >\n> > Actually, current man utilities locate the manual page by looking where\n> > the executable is, if MANPATH isn't defined (tested in Linux and\n> > Darwin).\n> >\n> > So, \"unset MANPATH; man git-add\" should be sufficient.\n> \n> That only works for paths registered in /etc/manpath.config (or an\n> equivalent config file depending on system/distribution).\n\nErr, no. I doubt my ~/opt/noarch/.../...; ~/opt/`uname -i`/git/; etc.,\nare pre-registered by my Linux distro or OS X 10.[45].\n\nman man:\n If you specify the -M pathlist option, pathlist is a colon-separated\n list of the directories that man searches.\n\n If you don’t specify -M but set the MANPATH environment variable, the\n value of that variable is the list of the directories that man\n searches.\n\n If you don’t specify an explicit path list with -M or MANPATH, man\n develops its own path list based on the contents of the configuration\n file /etc/man.config. The MANPATH statements in the configuration file\n identify particular directories to include in the search path.\n...\n In addition, for each directory in the command search path (we’ll call\n it a \"command directory\") for which you do not have a MANPATH_MAP\n statement, man automatically looks for a manual page directory \"nearby\"\n namely as a subdirectory in the command directory itself or in the par-\n ent directory of the command directory.\n\nSo, according to the last paragraph, and assuming no -M argument and no\nMANPATH environment variable are defined, man should be able to find the\nmanual pages for git commands if they're in PATH.\n\n-- \nLuciano Rocha \nEurotux Informática, S.A. \n"},{"id":"62177","messageId":"87k5nr7jse.fsf@osv.gnss.ru","threadId":"11130","inReplyTo":"7vr6i245b4.fsf@gitster.siamese.dyndns.org","subject":"Re: git help error","fromName":"Sergei Organov","fromEmail":"osv@javad.com","sentAt":"2007-12-06T18:36:01Z","receivedAt":"2007-12-06T18:36:01Z","isPatch":false,"sender":{"key":"osv@javad.com","avatar":null},"body":"Junio C Hamano writes:\n\n> Sergei Organov writes:\n>\n>> Junio C Hamano writes:\n>>> \"Aneesh Kumar\" writes:\n>>>\n>>>> git help gives me the below error.\n>>>>\n>>>> [master@git]$ git help add\n>>>> No manual entry for git-add\n>>>> See 'man 7 undocumented' for help when manual pages are not available.\n>>>> [master@git]$\n>>>>\n>>>> I have the git binaries installed via --prefix\n>>>>\n>>>> ./configure --prefix=/home/kvaneesh/bin-local/git/\n>>>> and to see the man page i have to say\n>>>>\n>>>> man -M /home/kvaneesh/bin-local/git/share/man/\n>>> ...\n>>> When you run \"man\" from the command line, can you say\n>>>\n>>> $ man git-add\n>>>\n>>> and make it work? If it fails the same way, then what you are missing\n>>> is MANPATH environment variable, isn't it?\n>>\n>> I think what the OP asked for makes sense. git-help should better find\n>> corresponding version of manual pages automatically. This way, if one\n>> invokes different versions of git-help, he will get corresponding\n>> version of help text.\n>\n> I do not necessarily agree. Read what Aneesh wrote originally again,\n> and read what he _didn't_ write.\n>\n> Not only he needs to run his \"man\" with -M (and my point was that it is\n> not the only way, by the way), he needs to futz with his $PATH to\n> include $HOME/bin-local/git for _his_ installation to work.\n\nMy point is that he doesn't need to tweak his $PATH, because he can\nsimply say:\n\n$ ~/bin-local/git/bin/git help add\n\nThen, I'd expect that the manual page that is installed along with the\nversion that\n\n$ ~/bin-local/git/bin/git --version\n\nreports is displayed, not any random version of git-add manual page\nfound using default 'man' rules.\n\n> I think my suggestion to use $MANPATH is in line with what he is already\n> doing. If you install things in non-standard places, you can use\n> environments to adjust to what you did, and that's the reason PATH and\n> MANPATH environments are supported by your tools.\n\nYes, but provided you have more than one version of git installed, it's\ninconvenient to tweak both PATH and MANPATH to use one or another. It\nwould be more convenient and consistent if\n\n$ ~/git.old/bin/git help add\n$ ~/git.new/bin/git help add\n\nwere render different versions of git-add manual page, each\ncorresponding to the right version of git.\n\n> Having said that, I do not mind accepting a patch that prepends the\n> nonlocal path to MANPATH in help.c::show_man_page().\n\nOK, patch will follow shortly.\n\n-- \nSergei.\n"}]}