Re: [PATCH 1/2] Documentation: config: add "browser.<tool>.path".
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 28, 2008, 07:36 UTC
- Message-ID
- <7v1w82wgev.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <20080128080223.de8a67d2.chriscool@tuxfamily.org>
Christian Couder <chriscool@tuxfamily.org> writes:
Show 17 quoted lines
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org> > --- > Documentation/config.txt | 4 ++++ > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 877eda9..c2fedd1 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -367,6 +367,10 @@ branch.<name>.rebase:: > it unless you understand the implications (see linkgit:git-rebase[1] > for details). > > +browser.<tool>.path:: > + Override the path for the given tool that may be used to > + browse help. See linkgit:git-help[1]. > +
Thanks.
I wonder if we want to stress the fact that this is about rendering HTML version of the manual. IOW, the <tool>.path is about the path the chosen HTML renderer program is at, and not consulted at all unless "git help -w help" is run.
Also, do we want to list the repertoire of <tool>? Unlike <name> in "remote.<name>.url" and "branch.<name>.remote", this is not something the end user can arbitrarily name.
Incidentally, I notice that git-help manual page does not list what browsers are supported (except that it hints that firefox is usable by having an example "browser.firefox.path"), even though it tells how the browser is picked via "*.browser".