From: tilo@tilo-schwarz.de
To: jonas.fonseca@gmail.com
Cc: git@vger.kernel.org, Tilo Schwarz <tilo@tilo-schwarz.de>
Subject: [tig PATCH 0/1] Make height of split view configurable
Date: Mon, 23 Feb 2009 23:24:02 +0100 [thread overview]
Message-ID: <cover.1235338009.git.tilo@tilo-schwarz.de> (raw)
Rationale: On a large display with many rows it would be nice to be
able to configure the heights of the views in the split view. For
example, I like to have the lower diff view be 90% of the total
view height.
As it is, the patch lets the height of the lower view be configurable.
Is it may be better to configure the height of the upper view?
Any input on variable nameing, code style etc. of course welcome.
Tilo Schwarz (1):
Make height of split view configurable
NEWS | 3 +++
tig.c | 30 +++++++++++++++++++-----------
tigrc.5.txt | 8 ++++++++
3 files changed, 30 insertions(+), 11 deletions(-)
next reply other threads:[~2009-02-23 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 22:24 tilo [this message]
2009-02-23 22:24 ` [PATCH 1/1] Make height of split view configurable tilo
2009-02-25 22:17 ` [tig PATCH 0/1] " Jonas Fonseca
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=cover.1235338009.git.tilo@tilo-schwarz.de \
--to=tilo@tilo-schwarz.de \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.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 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).