From: Gustaf Hendeby <hendeby@isy.liu.se>
To: git@vger.kernel.org
Cc: Gustaf Hendeby <hendeby@isy.liu.se>
Subject: [PATCH] Documentation/config.txt: Add git-gui options
Date: Tue, 6 May 2008 21:39:05 +0200 [thread overview]
Message-ID: <1210102745-7415-1-git-send-email-hendeby@isy.liu.se> (raw)
The 'git gui' has a number of options that can be specified using the
options dialog. Sometimes it is convenient to be able to specify these
from the command line, therefor document these options.
Signed-off-by: Gustaf Hendeby <hendeby@isy.liu.se>
---
This manual update was initiated by the problem with git gui freezing
up at start when only aspell previous to version 0.6 is available.
For the moment a fix is to set gui.spellingdictionary="none", however
this option isn't documented anywhere but in code. I think it would
be nice to have this option and other used by git gui documented
somewhere, even if for no other reason than to understand what is in
your .gitconfig.
This patch introduces some more of the git gui specific options in
config.txt with the reset of the git options (as suggested by Shawn.).
An option would be to put the documentation in git-gui.txt and link to
there from config.txt. This way the config documentation does get
less cluttered, and it makes it possible to have different
documentation for different versions of git gui. Does anyone have any
opinions? Maybe it is only me that think the options needs to be
documented at?
/Gustaf
Documentation/config.txt | 31 +++++++++++++++++++++++++++++++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index fe43b12..06ab05e 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -673,6 +673,37 @@ specified as 'gitcvs.<access_method>.<varname>' (where 'access_method'
is one of "ext" and "pserver") to make them apply only for the given
access method.
+gui.commitmsgwidth::
+ Defines how wide the commit message window is in the
+ linkgit:git-gui[1]. "75" is the default.
+
+gui.diffcontext::
+ Specify how many context lines should be used by in calls to
+ diff made in the linkgit:git-gui[1]. The default is "5".
+
+gui.matchtrackingbranch::
+ Determine if new branches created with linkgit:git-gui[1] should
+ default to track remote branches with matching names. Default:
+ "false".
+
+gui.newbranchtemplate::
+ Is used as suggested name when creating new branches using the
+ linkgit:git-gui[1].
+
+gui.pruneduringfetch::
+ "true" if linkgit:git-gui[1] should prune tracking branches when
+ performing a fetch. The default value is "false".
+
+gui.trustmtime::
+ Determine if linkgit:git-gui[1] should trust the file modification
+ timestamp or not. By default the timestamps are not trusted.
+
+gui.spellingdictionary::
+ Specify the dictionary used for spell checking commit messages in
+ the linkgit:git-gui[1]. When set to "none" spelling is turned off,
+ making linkgit:git-gui[1] to start on systems with aspell previous
+ to version 0.6.
+
help.browser::
Specify the browser that will be used to display help in the
'web' format. See linkgit:git-help[1].
--
1.5.5.1.273.g1810b
next reply other threads:[~2008-05-06 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 19:39 Gustaf Hendeby [this message]
2008-05-07 23:09 ` [PATCH] Documentation/config.txt: Add git-gui options Shawn O. Pearce
2008-05-08 8:55 ` [PATCH v2] " Gustaf Hendeby
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=1210102745-7415-1-git-send-email-hendeby@isy.liu.se \
--to=hendeby@isy.liu.se \
--cc=git@vger.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).