From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Edgar Toernig" <froese@gmx.de>
Cc: "Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org, "Paul Mackerras" <paulus@samba.org>
Subject: Re: gitk lower pane (commit and files view) scrollbar extends past gitk window
Date: Thu, 22 Jun 2006 09:10:24 +0200 [thread overview]
Message-ID: <81b0412b0606220010p6c2e62ffv3914abafd95e4bb2@mail.gmail.com> (raw)
In-Reply-To: <20060622023546.28cb4291.froese@gmx.de>
On 6/22/06, Edgar Toernig <froese@gmx.de> wrote:
> Jakub Narebski wrote:
> >
> > In gitk from the current 'next' branch, post git version 1.4.0
> > (blob ba4644f) scrollbar for lower pane, i.e. for commitdiff and files
> > (Comments) views extends past the bottom of the gitk window. Therefore
> > I cannnot see lower part of commit diff if it is larger than window height.
>
> Yes, and the search field at the bottom is invisible too. Removing
> line 431:
>
> .ctop conf -width $geometry(width) -height $geometry(height)
>
> seems to fix it and the window still gets the right size.
>
No, it does not. It gets the default geometry, not the one it had last time.
next prev parent reply other threads:[~2006-06-22 7:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 12:42 gitk lower pane (commit and files view) scrollbar extends past gitk window Jakub Narebski
2006-06-22 0:35 ` Edgar Toernig
2006-06-22 6:52 ` [PATCH] gitweb: whitespace cleanup around '=' Jakub Narebski
2006-06-22 7:01 ` Jakub Narebski
2006-06-22 7:09 ` Junio C Hamano
2006-06-22 7:32 ` Jakub Narebski
2006-06-22 9:33 ` Junio C Hamano
2006-06-22 9:37 ` Jakub Narebski
2006-06-22 10:20 ` Junio C Hamano
2006-06-22 9:52 ` Jakub Narebski
2006-06-22 10:19 ` Santi Béjar
2006-06-22 7:10 ` Alex Riesen [this message]
2006-06-22 7:48 ` [WORKAROUND] gitk lower pane scrollbar extends past gitk window Jakub Narebski
2006-06-22 13:19 ` Jakub Narebski
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=81b0412b0606220010p6c2e62ffv3914abafd95e4bb2@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=froese@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--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).