git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: no luck with colors for branch names in gitk yet

From
Philip Oakley <philipoakley@iee.org>
Date
Feb 5, 2016, 21:14 UTC
Message-ID
<B88DD991725D43E19185D46EED20FDDF@PhilipOakley>
In-Reply-To
<CAC4O8c-MPwrJ2H+iHjQxk+XoX4_vPm80Lz1=wbuHHd2gsB8R0Q@mail.gmail.com>
From: "Britton Kerin" <britton.kerin@gmail.com>
Show 11 quoted lines
> 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 )

--
Philip
Previous: Britton KerinNext: Britton Kerin
Message 2 of 4 in “no luck with colors for branch names in gitk yet”
  1. Britton KerinFeb 5, 2016
  2. Philip OakleyFeb 5, 2016
  3. Britton KerinFeb 5, 2016
  4. John KeepingFeb 5, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.