From: Manuel Bua <manuel.bua@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] gitk: Add user-configurable branch bg color
Date: Sun, 17 Mar 2013 13:46:57 +0100 [thread overview]
Message-ID: <5145BB41.3020406@gmail.com> (raw)
In-Reply-To: <CAJDDKr5XqX3dKLEiOAo7VeaofN37Q8aAN=GyMVf5-bGiiv9FDw@mail.gmail.com>
On 03/17/2013 03:57 AM, David Aguilar wrote:
>
> > In some cases, the default branch background color (green) isn't
> > an optimal choice, thus it can be difficult to read.
>
> I'm just curious -- is it "difficult to read" because gitk does not
> specify a foreground color, thus causing it to pickup a system default
> (which can vary), or is it for a different reason?
>
> If this is the reason then I wonder whether gitk should explicitly set
> a foreground color. Apologies if it already works that way -- I just
> wanted to better understand the motivation behind this patch.
>
Yes, having gitk to specify a foreground color instead would probably
solve it too: i can remember the branch rectangles were a lot more
readable in the past, but this could probably be due to me using a dark
system theme at the time.
For example, in my case it would look a lot more readable if the text
was "white on green" instead of "black on green", that could be even
hardcoded as it was with the "green" color, but the reason behind the
choice to let the user customize it is that i think it is better to
honour the user system colors giving the means to adjust it to match his
actual system configuration, rather than overriding it.
Regards,
Manuel
prev parent reply other threads:[~2013-03-17 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 20:05 [PATCH] gitk: Add user-configurable branch bg color Manuel Bua
[not found] ` <CAJDDKr5XqX3dKLEiOAo7VeaofN37Q8aAN=GyMVf5-bGiiv9FDw@mail.gmail.com>
2013-03-17 12:46 ` Manuel Bua [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=5145BB41.3020406@gmail.com \
--to=manuel.bua@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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).