From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Make gitk work reasonably well on Cygwin.
Date: Wed, 31 Jan 2007 17:28:44 +0100 [thread overview]
Message-ID: <45C0C3BC.BD01337E@eudaptics.com> (raw)
In-Reply-To: BAY13-F213DF79906B3889D42369D0A50@phx.gbl
Mike Nefari wrote:
>
> The gitk gui layout was completely broken on Cygwin. If gitk was started
> without previous geometry in ~/.gitk, the user could drag the window sashes
> to get a useable layout. However, if ~/.gitk existed, this was not possible
> at all.
>
> The fix was to rewrite makewindow, changing the toplevel containers and
> the particular geometry information saved between sessions. Numerous bugs
> in both the Cygwin and the Linux Tk versions make this a delicate
> balancing act: the version here works in both but many subtle variants
> are competely broken in one or the other environment.
Your mailer has garbled your patch. But once this is fixed, it works
quite well, both on my Linux box with Tk 8.4, where gitk's layout was
suboptimal, as well as under MinGW, also with Tk 8.4.
Thank you, you saved my day!
-- Hannes
next prev parent reply other threads:[~2007-01-31 16:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 14:50 [PATCH] Make gitk work reasonably well on Cygwin Mike Nefari
2007-01-31 15:17 ` Johannes Schindelin
2007-01-31 16:00 ` Mark Levedahl
2007-01-31 16:33 ` Johannes Sixt
2007-01-31 16:44 ` Johannes Schindelin
2007-02-01 1:41 ` Mark Levedahl
2007-02-01 3:22 ` Junio C Hamano
2007-02-01 5:24 ` Seth Falcon
2007-02-01 8:03 ` Alex Riesen
2007-02-01 14:03 ` Mark Levedahl
2007-02-01 19:24 ` Shawn O. Pearce
2007-02-01 9:20 ` Johannes Schindelin
2007-02-01 13:56 ` Mark Levedahl
2007-02-01 14:05 ` Johannes Schindelin
2007-02-01 15:04 ` Mark Levedahl
2007-02-01 15:28 ` Christian MICHON
2007-02-01 15:39 ` Johannes Sixt
2007-02-01 16:00 ` Johannes Schindelin
2007-02-01 17:33 ` Mark Levedahl
2007-02-01 2:09 ` Mark Levedahl
2007-01-31 16:28 ` Johannes Sixt [this message]
2007-01-31 16:36 ` Alex Riesen
2007-01-31 16:39 ` Mark Levedahl
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=45C0C3BC.BD01337E@eudaptics.com \
--to=j.sixt@eudaptics.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.
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.