{"thread":{"id":"41345","subject":"no luck with colors for branch names in gitk yet","startedAt":"2016-02-05T20:48:33Z","lastAt":"2016-02-05T23:28:49Z","messageCount":4,"participants":["Britton Kerin","Philip Oakley","John Keeping"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"277593","messageId":"CAC4O8c-MPwrJ2H+iHjQxk+XoX4_vPm80Lz1=wbuHHd2gsB8R0Q@mail.gmail.com","threadId":"41345","inReplyTo":null,"subject":"no luck with colors for branch names in gitk yet","fromName":"Britton Kerin","fromEmail":"britton.kerin@gmail.com","sentAt":"2016-02-05T20:48:33Z","receivedAt":"2016-02-05T20:48:33Z","isPatch":false,"sender":{"key":"britton.kerin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/7434164?v=4"},"body":"Someone suggested using color.branch.upstream, I tried like this and variants\n\n[color \"branch\"]\n local = red bold\n upstream = red bold\n\nDoesn't seem to matter what I put in for upstream, including invalid\ncolors, gitk just ignores it and does the dark green for local\nbranches\n"},{"id":"277599","messageId":"B88DD991725D43E19185D46EED20FDDF@PhilipOakley","threadId":"41345","inReplyTo":"CAC4O8c-MPwrJ2H+iHjQxk+XoX4_vPm80Lz1=wbuHHd2gsB8R0Q@mail.gmail.com","subject":"Re: no luck with colors for branch names in gitk yet","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":null,"receivedAt":"2016-02-05T21:14:35Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Britton Kerin\" \n> Someone suggested using color.branch.upstream, I tried like this and \n> variants\n>\n> [color \"branch\"]\n> local = red bold\n> upstream = red bold\n>\n> Doesn't seem to matter what I put in for upstream, including invalid\n> colors, gitk just ignores it and does the dark green for local\n> branches\n> --\nAlternate, try\nhttps://github.com/oumu/mintty-color-schemes/blob/master/base16-mintty/base16-default.minttyrc\n(or any of the other colour schemes) and copy them into your .minttyrc file\n(works for me on g4w : git version 2.7.0.windows.1 )\n\n--\n\nPhilip \n"},{"id":"277612","messageId":"CAC4O8c81h-JEGN2mS=SgUnBQM+A-RojDBOY65f=Jmubo6CZCwA@mail.gmail.com","threadId":"41345","inReplyTo":"B88DD991725D43E19185D46EED20FDDF@PhilipOakley","subject":"Re: no luck with colors for branch names in gitk yet","fromName":"Britton Kerin","fromEmail":"britton.kerin@gmail.com","sentAt":"2016-02-05T22:29:26Z","receivedAt":"2016-02-05T22:29:26Z","isPatch":false,"sender":{"key":"britton.kerin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/7434164?v=4"},"body":"On Fri, Feb 5, 2016 at 12:25 PM, Philip Oakley wrote:\n> From: \"Britton Kerin\" \n>>\n>> Someone suggested using color.branch.upstream, I tried like this and\n>> variants\n>>\n>> [color \"branch\"]\n>> local = red bold\n>> upstream = red bold\n>>\n>> Doesn't seem to matter what I put in for upstream, including invalid\n>> colors, gitk just ignores it and does the dark green for local\n>> branches\n>> --\n>\n> Alternate, try\n> https://github.com/oumu/mintty-color-schemes/blob/master/base16-mintty/base16-default.minttyrc\n> (or any of the other colour schemes) and copy them into your .minttyrc file\n> (works for me on g4w : git version 2.7.0.windows.1 )\n\nI'm on linux so I think mintty is not an option. Also, I'm a little\nsurprised in affects the rendering of branch tags in gitk, I would\nhave thought that would be an X or window system thing.\n\nBritton\n"},{"id":"277617","messageId":"20160205232849.GJ29880@serenity.lan","threadId":"41345","inReplyTo":"CAC4O8c81h-JEGN2mS=SgUnBQM+A-RojDBOY65f=Jmubo6CZCwA@mail.gmail.com","subject":"Re: no luck with colors for branch names in gitk yet","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2016-02-05T23:28:49Z","receivedAt":"2016-02-05T23:28:49Z","isPatch":false,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"On Fri, Feb 05, 2016 at 01:29:26PM -0900, Britton Kerin wrote:\n> On Fri, Feb 5, 2016 at 12:25 PM, Philip Oakley wrote:\n> > From: \"Britton Kerin\" \n> >>\n> >> Someone suggested using color.branch.upstream, I tried like this and\n> >> variants\n> >>\n> >> [color \"branch\"]\n> >> local = red bold\n> >> upstream = red bold\n> >>\n> >> Doesn't seem to matter what I put in for upstream, including invalid\n> >> colors, gitk just ignores it and does the dark green for local\n> >> branches\n> >> --\n> >\n> > Alternate, try\n> > https://github.com/oumu/mintty-color-schemes/blob/master/base16-mintty/base16-default.minttyrc\n> > (or any of the other colour schemes) and copy them into your .minttyrc file\n> > (works for me on g4w : git version 2.7.0.windows.1 )\n> \n> I'm on linux so I think mintty is not an option. Also, I'm a little\n> surprised in affects the rendering of branch tags in gitk, I would\n> have thought that would be an X or window system thing.\n\nI think Philip missed that you were talking about gitk. It seems that\nthe problem comes from updating to Tcl/Tk 7.6, which makes green darker\nas described in commit 66db14c (gitk: Color name update, 2015-10-25) and\nby TIP #403 [1].\n\nHowever, it seems that gitk won't actually use the updated colour if you\nhave an existing ~/.gitk file. You can just replace \"green\" with \"lime\"\nin that file to get the new defaults, but I wonder if we should force\nthat for users who already have the previous defaults saved.\n\n\n[1] http://www.tcl.tk/cgi-bin/tct/tip/403.html\n"}]}