git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Sean <seanlkml@sympatico.ca>
Cc: Paul Mackerras <paulus@samba.org>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: gitk with hyperspace support
Date: Fri, 2 Sep 2005 15:20:00 +0200	[thread overview]
Message-ID: <81b0412b0509020620559ab811@mail.gmail.com> (raw)
In-Reply-To: <51773.10.10.10.10.1125609974.squirrel@linux1>

On 9/1/05, Sean <seanlkml@sympatico.ca> wrote:
> > BTW, did you sometimes notice lines you can't click at all?
> > An example is the red line on the most left side of the graph
> > by SHA 66129f88c4cc719591f687e5c8c764fe9d3e437a.
> For what it's worth, everything near that SHA1 works here as expected.
> Although I wasn't able to follow what you meant by "blue up-arrow through
> green left bump..." etc.   But all the lines respond to being clicked and
> all the arrow heads in that area properly jump to their corresponding
> commit.
> 
> That's with the latest checked out version of git and tcl/tk 8.4.9 as well.

I just tested it on another system (8.4.6, Slackware 10+), and it works
correctly too. Probably it is Gentoo's (or mine, you never know in Gentoo)
Tcl/Tk, which is broken somewhere.

  reply	other threads:[~2005-09-02 13:20 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
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 [this message]
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=81b0412b0509020620559ab811@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=paulus@samba.org \
    --cc=seanlkml@sympatico.ca \
    /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).