git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustaf Hendeby <hendeby@isy.liu.se>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Benjamin Collins <ben.collins@acm.org>, git@vger.kernel.org
Subject: Re: git-gui hangs on read
Date: Fri, 25 Apr 2008 08:45:40 +0200	[thread overview]
Message-ID: <48117E14.7010505@isy.liu.se> (raw)
In-Reply-To: <20080425010245.GZ29771@spearce.org>

On 04/25/2008 03:02 AM, Shawn O. Pearce wrote:
> Gustaf Hendeby <hendeby@isy.liu.se> wrote:
>> On 04/24/2008 03:00 AM, Shawn O. Pearce wrote:
>>> Just turn the d**n spell checker off:
>>>
>>> 	git config --global gui.spellingdictionary none
>>>
>>> That will keep us from evening trying to launch aspell, and since
>>> its global (in your ~/.gitconfig) it should default into every
>>> repository you have, or create.
>> Thanks, even better!  Though, I can't seem to find this option (and 
>> other ones indicated by the source) documented anywhere.  Where would be 
>> the place to put such information?  For git options the place seems to 
>> be the git config help, but given that the git gui is maintained 
>> independently the choice is less obvious to me.
> 
> As far as documenting the git-gui options, maybe they should go into
> either Documentation/git-gui.txt or into Documentation/config.txt
> in the main git.git project.  The latter almost makes sense because
> git-gui does store its preferences in the same config file, and that
> file describes the valid keys and what they mean.
> 

My first thought about the documentation was to put it in 
Documentation/config.txt but wouldn't that be strange if someone uses a 
git-gui other than the one bundled with the git version used?  On the 
other hand, if the keys don't ever change that is not a big problem.

I'll try to have a go at writing some docs, but it won't be until late 
next week because my daytime work is killing me right now.

/Gustaf

      reply	other threads:[~2008-04-25  6:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 14:23 git-gui hangs on read Benjamin Collins
2008-04-21 21:05 ` Benjamin Collins
2008-04-22  0:13 ` Shawn O. Pearce
2008-04-22 13:34   ` Benjamin Collins
2008-04-22 23:25     ` Shawn O. Pearce
2008-04-23  8:50       ` Gustaf Hendeby
2008-04-23 14:16         ` Benjamin Collins
2008-04-23 14:49           ` Gustaf Hendeby
2008-04-24  1:00             ` Shawn O. Pearce
2008-04-24  6:54               ` Gustaf Hendeby
2008-04-25  1:02                 ` Shawn O. Pearce
2008-04-25  6:45                   ` Gustaf Hendeby [this message]

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=48117E14.7010505@isy.liu.se \
    --to=hendeby@isy.liu.se \
    --cc=ben.collins@acm.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).