git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <stefan.naewe@atlas-elektronik.com>
To: <eric.frederich@gmail.com>, <git@vger.kernel.org>
Subject: Re: [BUG] gitk
Date: Wed, 8 Jun 2016 09:58:49 +0000	[thread overview]
Message-ID: <2103a5a2-6936-0d2c-9a07-bb0713153d82@atlas-elektronik.com> (raw)
In-Reply-To: <4c22a048-ad42-c831-e167-5be5540bdb49@atlas-elektronik.com>


[-- Attachment #1.1: Type: text/plain, Size: 1954 bytes --]

Am 08.06.2016 um 11:40 schrieb stefan.naewe@atlas-elektronik.com:
> Am 07.06.2016 um 21:20 schrieb Eric Frederich:
>> Hello,
>>
>> I couldn’t find any documentation on submitting patches for gitk.
>> I saw in Documentation/SubmittingPatches that gitk is maintained in
>> its own repo.
>> I can’t clone repo’s unless they’re http while on my corporate proxy.
>> I’m hoping someone can help me out or just do it for me ;-)
>> I’d like to revert 66db14c94c95f911f55575c7fdf74c026443d482.
>>
>> That commit just renamed “green” to “lime”
>> It causes gitk to not start up on when ran through VNC.
>> It works fine on that same system natively or over X11 forwarding but not VNC.
> 
> FWIW, I can confirm that.
> 
> git version 2.8.3
> 
> My $HOME/.config/git/gitk contains:
> 
> set mergecolors {red blue green purple brown "#009090" magenta "#808000" "#009000" "#ff0080" cyan "#b07070" "#70b0f0" "#70f0b0" "#f0b070" "#ff70b0"}
> 
> With that file gitk runs without problems.
> If I move that file away, gitk stops working over VNC and also forwarded X11 for me.

More Info:

The forwarded X11 (which is from a Windows machine running Exceed to a Linux machine) works
without the gitk file mentioned above, if I edit the 'rgb.txt' used by Exceed to contain something like:

 50 205  50		lime

Before the editing the file only contained the following:

 50 205  50		lime green
 50 205  50		LimeGreen

I couldn't do the same for the VNC connection though (Xvnc seems to use a hardcoded 'rgb.txt' file).

It seems that using 'lime' was not the best choice...


HTH

Stefan
-- 
----------------------------------------------------------------
/dev/random says: I used to be schizophrenic, but we're all right now.
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')" 
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9  9666 829B 49C5 9221 27AF


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-06-08 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 19:20 [BUG] gitk Eric Frederich
2016-06-08  9:40 ` stefan.naewe
2016-06-08  9:58   ` stefan.naewe [this message]
2016-06-08 12:31     ` Eric Frederich
2016-06-08 12:42       ` stefan.naewe
2016-06-08 15:36       ` Mike Rappazzo

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2103a5a2-6936-0d2c-9a07-bb0713153d82@atlas-elektronik.com \
    --to=stefan.naewe@atlas-elektronik.com \
    --cc=eric.frederich@gmail.com \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).