From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Taeung Song <treeze.taeung@gmail.com>
Subject: [PATCH 5/8] perf config: Document 'man.viewer' variable in man page
Date: Thu, 4 Feb 2016 18:25:10 +0900 [thread overview]
Message-ID: <1454577913-16401-6-git-send-email-treeze.taeung@gmail.com> (raw)
In-Reply-To: <1454577913-16401-1-git-send-email-treeze.taeung@gmail.com>
Explain 'man.viewer' variable and how to add
new man viewer tools.
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
---
tools/perf/Documentation/perf-config.txt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/tools/perf/Documentation/perf-config.txt b/tools/perf/Documentation/perf-config.txt
index 0154bc9..a30d225 100644
--- a/tools/perf/Documentation/perf-config.txt
+++ b/tools/perf/Documentation/perf-config.txt
@@ -410,6 +410,15 @@ top.*::
as well as 'Self' overhead column by default.
The default is true.
+man.*::
+ man.viewer::
+ This option can assign a tool to view manual pages when 'help'
+ subcommand was invoked. Supported tools are 'man', 'woman'
+ (with emacs client) and 'konqueror'. Default is 'man'.
+
+ New man viewer tool can be also added using 'man.<tool>.cmd'
+ or use different path using 'man.<tool>.path' config option.
+
SEE ALSO
--------
linkperf:perf[1]
--
2.5.0
next prev parent reply other threads:[~2016-02-04 9:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 9:25 [PATCH 0/8] perf config: Document config variables in man page Taeung Song
2016-02-04 9:25 ` [PATCH 1/8] perf config: Document 'ui.show-headers' variable " Taeung Song
2016-02-09 12:10 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 9:25 ` [PATCH 2/8] perf config: Document variables for 'call-graph' section " Taeung Song
2016-02-09 12:10 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 9:25 ` [PATCH 3/8] perf config: Document variables for 'report' " Taeung Song
2016-02-09 12:11 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 9:25 ` [PATCH 4/8] perf config: Document 'top.children' variable " Taeung Song
2016-02-09 12:11 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 9:25 ` Taeung Song [this message]
2016-02-09 12:12 ` [tip:perf/core] perf config: Document 'man.viewer' " tip-bot for Taeung Song
2016-02-04 9:25 ` [PATCH 6/8] perf config: Document 'pager.<subcommand>' variables " Taeung Song
2016-02-09 12:12 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 9:25 ` [PATCH 7/8] perf config: Document 'kmem.default' variable " Taeung Song
2016-02-09 12:12 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 9:25 ` [PATCH 8/8] perf config: Document 'record.build-id' " Taeung Song
2016-02-09 12:13 ` [tip:perf/core] " tip-bot for Taeung Song
2016-02-04 14:49 ` [PATCH 0/8] perf config: Document config variables " Arnaldo Carvalho de Melo
2016-02-05 10:41 ` Taeung Song
2016-02-05 11:03 ` Taeung Song
2016-02-05 13:04 ` Namhyung Kim
2016-02-05 13:39 ` Arnaldo Carvalho de Melo
2016-02-05 13:42 ` Taeung Song
2016-02-05 13:44 ` Namhyung Kim
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=1454577913-16401-6-git-send-email-treeze.taeung@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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).