it unless you understand the implications (see linkgit:git-rebase[1]
for details).
+browser.<tool>.cmd::
+ Specify the command to invoke the specified browser. The
+ specified command is evaluated in shell with the URLs passed
+ as arguments. (See linkgit:git-web--browse[1].)
+
browser.<tool>.path::
Override the path for the given tool that may be used to
browse HTML help (see '-w' option in linkgit:git-help[1]) or a
</p>\r
<div class="literalblock">\r
<div class="content">\r
-<pre><tt>y - add the change from that hunk to index\r
-n - do not add the change from that hunk to index\r
-a - add the change from that hunk and all the rest to index\r
-d - do not the change from that hunk nor any of the rest to index\r
-j - do not decide on this hunk now, and view the next\r
- undecided hunk\r
-J - do not decide on this hunk now, and view the next hunk\r
-k - do not decide on this hunk now, and view the previous\r
- undecided hunk\r
-K - do not decide on this hunk now, and view the previous hunk\r
+<pre><tt>y - stage this hunk\r
+n - do not stage this hunk\r
+a - stage this and all the remaining hunks in the file\r
+d - do not stage this hunk nor any of the remaining hunks in the file\r
+j - leave this hunk undecided, see next undecided hunk\r
+J - leave this hunk undecided, see next hunk\r
+k - leave this hunk undecided, see previous undecided hunk\r
+K - leave this hunk undecided, see previous hunk\r
s - split the current hunk into smaller hunks\r
? - print help</tt></pre>\r
</div></div>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 21-Feb-2008 02:29:23 UTC\r
+Last updated 14-Mar-2008 08:58:15 UTC\r
</div>\r
</div>\r
</body>\r
and the working tree file and asks you if you want to stage
the change of each hunk. You can say:
- y - add the change from that hunk to index
- n - do not add the change from that hunk to index
- a - add the change from that hunk and all the rest to index
- d - do not the change from that hunk nor any of the rest to index
- j - do not decide on this hunk now, and view the next
- undecided hunk
- J - do not decide on this hunk now, and view the next hunk
- k - do not decide on this hunk now, and view the previous
- undecided hunk
- K - do not decide on this hunk now, and view the previous hunk
+ y - stage this hunk
+ n - do not stage this hunk
+ a - stage this and all the remaining hunks in the file
+ d - do not stage this hunk nor any of the remaining hunks in the file
+ j - leave this hunk undecided, see next undecided hunk
+ J - leave this hunk undecided, see next hunk
+ k - leave this hunk undecided, see previous undecided hunk
+ K - leave this hunk undecided, see previous hunk
s - split the current hunk into smaller hunks
? - print help
+
</p>\r
</dd>\r
<dt>\r
+browser.<tool>.cmd\r
+</dt>\r
+<dd>\r
+<p>\r
+ Specify the command to invoke the specified browser. The\r
+ specified command is evaluated in shell with the URLs passed\r
+ as arguments. (See <a href="git-web--browse.html">git-web--browse(1)</a>.)\r
+</p>\r
+</dd>\r
+<dt>\r
browser.<tool>.path\r
</dt>\r
<dd>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 13-Mar-2008 07:53:35 UTC\r
+Last updated 14-Mar-2008 08:58:15 UTC\r
</div>\r
</div>\r
</body>\r
</p>\r
</li>\r
</ul>\r
+<p>Custom commands may also be specified.</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
</div>\r
<h2>CONFIGURATION VARIABLES</h2>\r
<div class="sectionbody">\r
+<h3>CONF.VAR (from -c option) and web.browser</h3>\r
<p>The web browser can be specified using a configuration variable passed\r
with the -c (or --config) command line option, or the <em>web.browser</em>\r
configuration variable if the former is not used.</p>\r
+<h3>browser.<tool>.path</h3>\r
<p>You can explicitly provide a full path to your preferred browser by\r
setting the configuration variable <em>browser.<tool>.path</em>. For example,\r
you can configure the absolute path to firefox by setting\r
<em>browser.firefox.path</em>. Otherwise, <em>git-web--browse</em> assumes the tool\r
is available in PATH.</p>\r
+<h3>browser.<tool>.cmd</h3>\r
+<p>When the browser, specified by options or configuration variables, is\r
+not among the supported ones, then the corresponding\r
+<em>browser.<tool>.cmd</em> configuration variable will be looked up. If this\r
+variable exists then "git web--browse" will treat the specified tool\r
+as a custom command and will use a shell eval to run the command with\r
+the URLs passed as arguments.</p>\r
+<h3>Note about git config --global</h3>\r
<p>Note that these configuration variables should probably be set using\r
the <em>--global</em> flag, for example like this:</p>\r
<div class="listingblock">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 17-Feb-2008 03:50:09 UTC\r
+Last updated 14-Mar-2008 08:58:16 UTC\r
</div>\r
</div>\r
</body>\r
* dillo
* open (this is the default under Mac OS X GUI)
+Custom commands may also be specified.
+
OPTIONS
-------
-b BROWSER|--browser=BROWSER::
CONFIGURATION VARIABLES
-----------------------
+CONF.VAR (from -c option) and web.browser
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
The web browser can be specified using a configuration variable passed
with the -c (or --config) command line option, or the 'web.browser'
configuration variable if the former is not used.
+browser.<tool>.path
+~~~~~~~~~~~~~~~~~~~
+
You can explicitly provide a full path to your preferred browser by
setting the configuration variable 'browser.<tool>.path'. For example,
you can configure the absolute path to firefox by setting
'browser.firefox.path'. Otherwise, 'git-web--browse' assumes the tool
is available in PATH.
+browser.<tool>.cmd
+~~~~~~~~~~~~~~~~~~
+
+When the browser, specified by options or configuration variables, is
+not among the supported ones, then the corresponding
+'browser.<tool>.cmd' configuration variable will be looked up. If this
+variable exists then "git web--browse" will treat the specified tool
+as a custom command and will use a shell eval to run the command with
+the URLs passed as arguments.
+
+Note about git config --global
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
Note that these configuration variables should probably be set using
the '--global' flag, for example like this:
projects / git.git / commitdiff