git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Philip Oakley <philipoakley@iee.org>
Cc: Britton Kerin <britton.kerin@gmail.com>, git@vger.kernel.org
Subject: Re: changing colors in the tree view in gitk
Date: Sat, 6 Feb 2016 14:55:55 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1602061450300.2964@virtualbox> (raw)
In-Reply-To: <3FAE862069E24321A6E31D9F0CB66E35@PhilipOakley>

Hi Philip,

On Fri, 5 Feb 2016, Philip Oakley wrote:

> From: "Britton Kerin" <britton.kerin@gmail.com>
> >I upgraded from 2.5 to 2.7 and the branch names went from a light
> > green to dark green, the names of the tags are hard to read now.
> >
> > Is it possible to configure the branch name color in the tree view?
> > --
> Which Operating System is this on? and which Git version.?
> 
> 
> For the Git for Windows, the Mintty window colours can be adjusted. e.g.
> https://code.google.com/archive/p/mintty/wikis/Tips.wiki
> 
> Though I just changed my config setting for the awkward to read items (for me
> it was color.branch.upstream=green !)

I think Britton was talking about gitk, not about the console.

As it happens, this issue was already reported to the Git for Windows bug
tracker:

	https://github.com/git-for-windows/git/issues/300

It would appear that the culprit is a change in Tcl/Tk, not in gitk. I
outlined a possible solution in that ticket but have no plans to implement
that solution myself.

Ciao,
Johannes

      reply	other threads:[~2016-02-06 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 17:24 changing colors in the tree view in gitk Britton Kerin
2016-02-05 19:14 ` Philip Oakley
2016-02-06 13:55   ` Johannes Schindelin [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=alpine.DEB.2.20.1602061450300.2964@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=britton.kerin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.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).