From: John Keeping <john@keeping.me.uk>
To: Britton Kerin <britton.kerin@gmail.com>
Cc: Philip Oakley <philipoakley@iee.org>,
git@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: no luck with colors for branch names in gitk yet
Date: Fri, 5 Feb 2016 23:28:49 +0000 [thread overview]
Message-ID: <20160205232849.GJ29880@serenity.lan> (raw)
In-Reply-To: <CAC4O8c81h-JEGN2mS=SgUnBQM+A-RojDBOY65f=Jmubo6CZCwA@mail.gmail.com>
On Fri, Feb 05, 2016 at 01:29:26PM -0900, Britton Kerin wrote:
> On Fri, Feb 5, 2016 at 12:25 PM, Philip Oakley <philipoakley@iee.org> wrote:
> > From: "Britton Kerin" <britton.kerin@gmail.com>
> >>
> >> Someone suggested using color.branch.upstream, I tried like this and
> >> variants
> >>
> >> [color "branch"]
> >> local = red bold
> >> upstream = red bold
> >>
> >> Doesn't seem to matter what I put in for upstream, including invalid
> >> colors, gitk just ignores it and does the dark green for local
> >> branches
> >> --
> >
> > Alternate, try
> > https://github.com/oumu/mintty-color-schemes/blob/master/base16-mintty/base16-default.minttyrc
> > (or any of the other colour schemes) and copy them into your .minttyrc file
> > (works for me on g4w : git version 2.7.0.windows.1 )
>
> I'm on linux so I think mintty is not an option. Also, I'm a little
> surprised in affects the rendering of branch tags in gitk, I would
> have thought that would be an X or window system thing.
I think Philip missed that you were talking about gitk. It seems that
the problem comes from updating to Tcl/Tk 7.6, which makes green darker
as described in commit 66db14c (gitk: Color name update, 2015-10-25) and
by TIP #403 [1].
However, it seems that gitk won't actually use the updated colour if you
have an existing ~/.gitk file. You can just replace "green" with "lime"
in that file to get the new defaults, but I wonder if we should force
that for users who already have the previous defaults saved.
[1] http://www.tcl.tk/cgi-bin/tct/tip/403.html
prev parent reply other threads:[~2016-02-05 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 20:48 no luck with colors for branch names in gitk yet Britton Kerin
2016-02-05 21:25 ` Philip Oakley
2016-02-05 22:29 ` Britton Kerin
2016-02-05 23:28 ` John Keeping [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=20160205232849.GJ29880@serenity.lan \
--to=john@keeping.me.uk \
--cc=britton.kerin@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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).