From: Paul Mackerras <paulus@samba.org>
To: Pierre Habouzit <madcoder@debian.org>
Cc: git@vger.kernel.org
Subject: Re: New features in gitk
Date: Mon, 29 Oct 2007 10:13:43 +1100 [thread overview]
Message-ID: <18213.6055.235067.730640@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20071028183216.GA4310@artemis.corp>
Pierre Habouzit writes:
> As you seem to be the guy to ask for, I've a couple of requests wrt
> gitk.
>
> * the diff window is quite bad with merge commits, the colorization is
> rather poor, and the last version you just merged isn't especially
> better.
That's not a request, that's a grizzle. :) What would you like it to
look like?
> * the 'sha1' input field is a major pain in the UI: the cut&paste
> interaction is very poor. I don't know why, but it's often very very
> hard to really copy the sha id, probably because it's selected by
> default.
It's selected so that the contents are in the cut buffer and you can
paste them in an xterm with middle-button. Possibly I need to check
that control-C (or command-C under macos) is properly bound to copy.
> * the fact that it remembers the position where it was in the WM when
> it was closed is really annoying. the WM is supposed to place the
> window. With at least ion3 and xinerama it often shows up on the
> wrong screen. Remembering the window size though is fine.
That came in with some changes that make gitk start up correctly under
windows. I could see about making it set the window position only
under windows.
> * still wrt the layout, the focus is quite cumbersome. Gitk would be
> really really really nice to be used only from the keyboard, but
> because of a very unclear focus policy, it really isn't for me.
> Maybe it's just me, and I know this may not be 100% helpful, but I
> never know which part of gitk will receive my keys (history part,
> diff part, tree, ...).
What focus policy would you like?
Paul.
next prev parent reply other threads:[~2007-10-29 0:52 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 1:39 New features in gitk Paul Mackerras
2007-10-28 5:34 ` Linus Torvalds
2007-10-28 7:11 ` Paul Mackerras
2007-10-28 7:36 ` Steffen Prohaska
2007-10-28 16:50 ` Linus Torvalds
2007-11-01 10:00 ` Paul Mackerras
2007-11-01 15:16 ` Linus Torvalds
2007-11-02 10:19 ` Paul Mackerras
2007-11-02 12:44 ` Marco Costalba
2007-11-02 15:42 ` Linus Torvalds
2007-11-02 16:50 ` Marco Costalba
2007-11-02 18:16 ` Linus Torvalds
2007-11-02 20:31 ` [PATCH 0/2] History replay support Linus Torvalds
2007-11-02 20:32 ` [PATCH 1/2] Simplify topo-sort logic Linus Torvalds
2007-11-02 20:35 ` [PATCH 2/2] Support "history replay" for git log commands Linus Torvalds
2007-11-02 21:05 ` Junio C Hamano
2007-11-02 21:17 ` Linus Torvalds
2007-11-03 1:40 ` [PATCH 0/2] History replay support Linus Torvalds
2007-11-03 7:56 ` Marco Costalba
2007-11-03 18:11 ` [REPLACEMENT PATCH 2/2] Add "--early-output" log flag for interactive GUI use Linus Torvalds
2007-11-03 19:52 ` Marco Costalba
2007-11-04 3:06 ` Paul Mackerras
2007-11-04 5:38 ` Linus Torvalds
2007-11-04 7:10 ` Paul Mackerras
2007-11-04 7:52 ` Marco Costalba
2007-11-04 18:11 ` Linus Torvalds
2007-11-04 20:12 ` [PATCH 3/2] Enhance --early-output format Linus Torvalds
2007-11-05 20:24 ` Junio C Hamano
2007-11-05 20:47 ` Linus Torvalds
2007-11-05 21:22 ` Linus Torvalds
2007-11-05 21:35 ` Linus Torvalds
2007-11-13 4:58 ` [PATCH 4/2] Fix parent rewriting in --early-output Linus Torvalds
2007-11-13 5:43 ` Junio C Hamano
2007-11-13 6:46 ` Linus Torvalds
2007-11-13 7:16 ` Linus Torvalds
2007-11-13 7:53 ` Sven Verdoolaege
2007-11-13 8:48 ` Junio C Hamano
2007-11-13 8:01 ` Shawn O. Pearce
2007-11-13 8:24 ` Junio C Hamano
2007-11-13 9:59 ` Paul Mackerras
2007-11-13 18:53 ` Junio C Hamano
2007-11-13 21:55 ` Paul Mackerras
2007-11-16 7:30 ` Marco Costalba
2007-11-04 0:32 ` [PATCH 0/2] History replay support Paul Mackerras
2007-11-02 18:17 ` New features in gitk Johannes Schindelin
2007-11-02 15:03 ` Linus Torvalds
2007-11-01 11:37 ` Paul Mackerras
2007-11-01 15:47 ` Linus Torvalds
2007-11-01 16:21 ` Linus Torvalds
2007-10-28 18:32 ` Pierre Habouzit
2007-10-28 18:38 ` Mike Hommey
2007-10-28 23:13 ` Paul Mackerras [this message]
2007-10-29 6:20 ` Pierre Habouzit
2007-10-29 8:31 ` Jonathan del Strother
2007-10-29 6:24 ` Pierre Habouzit
2007-10-29 13:30 ` Han-Wen Nienhuys
2007-10-29 14:04 ` Michele Ballabio
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 22:22 new " Paul Mackerras
2005-06-27 22:49 ` Luc Van Oostenryck
2005-06-27 23:36 ` Paul Mackerras
2005-06-28 20:24 ` Luc Van Oostenryck
2005-06-28 1:21 ` Linus Torvalds
2005-06-28 23:41 ` Paul Mackerras
2005-06-28 6:22 ` Greg KH
2005-06-30 6:20 ` Junio C Hamano
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=18213.6055.235067.730640@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.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).