All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Aguilar <davvid@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Andrew Janke <floss@apjanke.net>,
	Paul Mackerras <paulus@samba.org>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: gitk: "lime" color incompatible with older Tk versions
Date: Fri, 13 Jan 2017 03:20:43 -0800	[thread overview]
Message-ID: <20170113112043.j7nowdilolswyk2k@gmail.com> (raw)
In-Reply-To: <CAGZ79kaO9T+Qc=M6s_ZdpAfLZCVQEYNF=zNxDWArDmsA7jjCWg@mail.gmail.com>

On Mon, May 02, 2016 at 09:20:43AM -0700, Stefan Beller wrote:
> + Paul Mackerras, who maintains gitk
> 
> On Sun, May 1, 2016 at 10:03 AM, Andrew Janke <floss@apjanke.net> wrote:
> > Hi, git folks,
> >
> > I'm having trouble running gitk on Mac OS X 10.9.5. The gitk program uses
> > the color "lime", which is not present in older versions of Tk, apparently
> > including the Tk 8.5 which ships with 10.9.

Ping.. it would be nice to get this patch applied.
I can verify that gitk on Mac OS X 10.11 also has this problem.
gitk is usually pretty good about backwards-compatibility.

> > This compatibility problem was noted before back in 2012, in
> > http://www.mail-archive.com/git%40vger.kernel.org/msg14496.html.
> >
> > Would you consider switching from lime to a hex value color, for
> > compatibility with users of older versions of Tk? A patch to do so is below;
> > only the file gitk-git/gitk needs to be changed.

I can recreate and resend this patch if needed; it's simply:
:%s/lime/"#99FF00"/g

Would a re-roll of this patch be accepted, or is it not worth
bothering?

Google for "gitk lime" to get a taste for some of the fallout
caused by this problem.

The fact that multiple pages, with different OS's, have examples
of users stumbling over this change is a good hint that it's
worth fixing.

Thoughts?
-- 
David

  reply	other threads:[~2017-01-13 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 17:03 gitk: "lime" color incompatible with older Tk versions Andrew Janke
2016-05-02 16:20 ` Stefan Beller
2017-01-13 11:20   ` David Aguilar [this message]
2017-01-14  8:48     ` gitk pull request // was: " David Aguilar
2017-01-15  2:35       ` Junio C Hamano
2017-01-16  3:17         ` Paul Mackerras
2017-01-16  7:48           ` Junio C Hamano
2017-01-17 18:34             ` Junio C Hamano
2017-01-18  3:52               ` [PATCH] gitk: remove translated message from comments David Aguilar
2017-01-18 10:15                 ` Paul Mackerras
2017-01-18 18:27                   ` Junio C Hamano

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=20170113112043.j7nowdilolswyk2k@gmail.com \
    --to=davvid@gmail.com \
    --cc=floss@apjanke.net \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sbeller@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.