From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: gitk with hyperspace support
Date: Wed, 17 Aug 2005 19:57:41 +1000 [thread overview]
Message-ID: <17155.2581.888904.526537@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <7vr7ct124c.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano writes:
> The new output looks a lot less cluttering and I like it very
> much, but it is confusing to me on one count. I clicked one
> arrowhead pointing downward, expecting that the pane would jump
> scroll to show the counterpart arrowhead, and was dissapointed
OK, you're the second person to ask for that, so I'll see what I can
do about it. I can think of 3 possible behaviors when you click on
the arrowhead:
1. scroll to bring the other arrowhead on-screen and briefly make it
larger or something similar to draw attention to it
2. scroll to bring the other arrowhead on-screen and warp the pointer
to it
3. select the next commit in the indicated direction which is a child
or parent that the line connects (scroll to make it visible,
highlight it, show its diff).
Which do you think would be best?
> > http://ozlabs.org/~paulus/gitk/gitk.hs
>
> I first thought you rewrote it in Haskell ;-).
Hmmm, maybe it's apache on ozlabs.org that is under that
misapprehension?
Thanks,
Paul.
next prev parent reply other threads:[~2005-08-17 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 0:21 gitk with hyperspace support Paul Mackerras
2005-08-17 3:02 ` Linus Torvalds
2005-08-17 6:58 ` Junio C Hamano
2005-08-17 8:13 ` Sean
2005-08-17 15:56 ` Matthias Urlichs
2005-08-17 9:57 ` Paul Mackerras [this message]
2005-08-17 22:34 ` Junio C Hamano
2005-08-30 1:46 ` Paul Mackerras
2005-08-30 7:50 ` Junio C Hamano
2005-09-01 20:10 ` Alex Riesen
2005-09-01 21:26 ` Sean
2005-09-02 13:20 ` Alex Riesen
2005-08-17 14:37 ` Matthias Urlichs
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17155.2581.888904.526537@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).