@matheusbsbs / matheus-bagliano / commits / 1658c6149a
Fork 0

Documention: web--browse: add info about "browser.<tool>.cmd" config var

Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Christian Couder committed Mar 14, 2008 at 05:56 UTC 1658c6149ac4462c874810c760507040122917e8
2 files changed +26
Documentation/config.txt
+5
@@ -420,6 +420,11 @@ branch.<name>.rebase::
420 it unless you understand the implications (see linkgit:git-rebase[1]
421 for details).
422
423 +browser.<tool>.cmd::
424 + Specify the command to invoke the specified browser. The
425 + specified command is evaluated in shell with the URLs passed
426 + as arguments. (See linkgit:git-web--browse[1].)
427 +
428 browser.<tool>.path::
429 Override the path for the given tool that may be used to
430 browse HTML help (see '-w' option in linkgit:git-help[1]) or a
Documentation/git-web--browse.txt
+21
@@ -27,6 +27,8 @@ The following browsers (or commands) are currently supported:
27 * dillo
28 * open (this is the default under Mac OS X GUI)
29
30 +Custom commands may also be specified.
31 +
32 OPTIONS
33 -------
34 -b BROWSER|--browser=BROWSER::
@@ -43,16 +45,35 @@ OPTIONS
45 CONFIGURATION VARIABLES
46 -----------------------
47
48 +CONF.VAR (from -c option) and web.browser
49 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
50 +
51 The web browser can be specified using a configuration variable passed
52 with the -c (or --config) command line option, or the 'web.browser'
53 configuration variable if the former is not used.
54
55 +browser.<tool>.path
56 +~~~~~~~~~~~~~~~~~~~
57 +
58 You can explicitly provide a full path to your preferred browser by
59 setting the configuration variable 'browser.<tool>.path'. For example,
60 you can configure the absolute path to firefox by setting
61 'browser.firefox.path'. Otherwise, 'git-web--browse' assumes the tool
62 is available in PATH.
63
64 +browser.<tool>.cmd
65 +~~~~~~~~~~~~~~~~~~
66 +
67 +When the browser, specified by options or configuration variables, is
68 +not among the supported ones, then the corresponding
69 +'browser.<tool>.cmd' configuration variable will be looked up. If this
70 +variable exists then "git web--browse" will treat the specified tool
71 +as a custom command and will use a shell eval to run the command with
72 +the URLs passed as arguments.
73 +
74 +Note about git config --global
75 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
76 +
77 Note that these configuration variables should probably be set using
78 the '--global' flag, for example like this:
79