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:33:35 +0100 [thread overview]
Message-ID: <45C0C4DF.C0EB4495@eudaptics.com> (raw)
In-Reply-To: Pine.LNX.4.63.0701311612420.22628@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> I also verified that with my Tcl/Tk installation on MacOSX, a patch like
> this was needed. IIRC Paulus argued that I should get a native TclTk,
> which is supposed to work (though not with the paths on Cygwin, oh well).
>
> Oh, and it is also needed for MinGW. But I guess it will remain unfixed.
You patch does not improve gitk under MinGW. The layout becomes less
useful because the lower part becomes too high, so that the Search bar
and some part of the patch + file list windows is not visible. :(
-- Hannes
next prev parent reply other threads:[~2007-01-31 16:35 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 [this message]
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
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=45C0C4DF.C0EB4495@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 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).