From: Christian Couder <chriscool@tuxfamily.org>
To: "Junio Hamano" <junkio@cox.net>, "Pascal Obry" <pascal@obry.net>,
"Xavier Maillard" <xma@gnu.org>
Cc: git@vger.kernel.org
Subject: [PATCH 2/5] documentation: help: add "man.<tool>.path" config variable
Date: Fri, 25 Apr 2008 08:24:41 +0200 [thread overview]
Message-ID: <20080425082441.9f2c7732.chriscool@tuxfamily.org> (raw)
This patch documents the "man.<tool>.path" configuration
variable.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
Documentation/config.txt | 4 ++++
Documentation/git-help.txt | 9 +++++++++
2 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index b109bdf..c1c72e7 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -773,6 +773,10 @@ man.viewer::
Specify the programs that may be used to display help in the
'man' format. See linkgit:git-help[1].
+man.<tool>.path::
+ Override the path for the given tool that may be used to
+ display help in the 'man' format. See linkgit:git-help[1].
+
include::merge-config.txt[]
mergetool.<tool>.path::
diff --git a/Documentation/git-help.txt b/Documentation/git-help.txt
index be2ae53..4c6cb21 100644
--- a/Documentation/git-help.txt
+++ b/Documentation/git-help.txt
@@ -104,6 +104,15 @@ DISPLAY is not set) and in that case emacs' woman mode will be tried.
If everything fails the 'man' program will be tried anyway.
+man.<tool>.path
+~~~~~~~~~~~~~~~
+
+You can explicitly provide a full path to your preferred man viewer by
+setting the configuration variable 'man.<tool>.path'. For example, you
+can configure the absolute path to konqueror by setting
+'man.konqueror.path'. Otherwise, 'git help' assumes the tool is
+available in PATH.
+
Note about git config --global
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
1.5.5.130.g3ab1e.dirty
reply other threads:[~2008-04-25 6:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080425082441.9f2c7732.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pascal@obry.net \
--cc=xma@gnu.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;
as well as URLs for NNTP newsgroup(s).