threads / discuss / 41342

changing colors in the tree view in gitk

Subject: changing colors in the tree view in gitk

## tl;dr

3 messages between Feb 5, 2016 and Feb 6, 2016.

replies: 2people: 3as markdown or json

Britton Kerin· Feb 5, 2016, 17:24 UTC · lore

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?

Philip Oakley· Feb 5, 2016, 19:05 UTC · re: Britton Kerin · lore

Re: changing colors in the tree view in gitk

From: "Britton Kerin" <britton.kerin@gmail.com>

Show 5 quoted lines

>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 !) --

Philip

Johannes Schindelin· Feb 6, 2016, 13:55 UTC · re: Philip Oakley · lore

Re: changing colors in the tree view in gitk

Hi Philip,

On Fri, 5 Feb 2016, Philip Oakley wrote:

Show 14 quoted lines

> 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