* Gitk: shortcut to jump to the current HEAD (yellow spot)?
@ 2011-12-22 15:49 Dirk Süsserott
2011-12-22 17:09 ` Martin von Zweigbergk
2011-12-22 18:26 ` Pat Thoyts
0 siblings, 2 replies; 7+ messages in thread
From: Dirk Süsserott @ 2011-12-22 15:49 UTC (permalink / raw)
To: Git Mailing List
Hi!
Does anybody know about a shortcut in gitk to "jump to the yellow spot"?
I often use cmdline and gitk at the same time, switch branches, stash,
rebase and so on from bash. When hitting [Ctrl-]F5 in gitk, the last
highlighted commit is focused again and my HEAD is far off the screen.
Is there a way to jump to the HEAD (the yellow bubble in gitk) with a
fingertip?
TIA
Dirk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Gitk: shortcut to jump to the current HEAD (yellow spot)?
2011-12-22 15:49 Gitk: shortcut to jump to the current HEAD (yellow spot)? Dirk Süsserott
@ 2011-12-22 17:09 ` Martin von Zweigbergk
2011-12-22 17:23 ` Dirk Süsserott
2011-12-22 18:26 ` Pat Thoyts
1 sibling, 1 reply; 7+ messages in thread
From: Martin von Zweigbergk @ 2011-12-22 17:09 UTC (permalink / raw)
To: Dirk Süsserott; +Cc: Git Mailing List
2011/12/22 Dirk Süsserott <newsletter@dirk.my1.cc>:
> Does anybody know about a shortcut in gitk to "jump to the yellow spot"?
Not sure it's fast enough for you, but you can always enter "HEAD" in
the "SHA1 ID" box (and press Enter).
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Gitk: shortcut to jump to the current HEAD (yellow spot)?
2011-12-22 15:49 Gitk: shortcut to jump to the current HEAD (yellow spot)? Dirk Süsserott
2011-12-22 17:09 ` Martin von Zweigbergk
@ 2011-12-22 18:26 ` Pat Thoyts
2011-12-23 18:54 ` Dirk Süsserott
1 sibling, 1 reply; 7+ messages in thread
From: Pat Thoyts @ 2011-12-22 18:26 UTC (permalink / raw)
To: Dirk Süsserott; +Cc: Git Mailing List
Dirk Süsserott <newsletter@dirk.my1.cc> writes:
>Hi!
>
>Does anybody know about a shortcut in gitk to "jump to the yellow spot"?
>
>I often use cmdline and gitk at the same time, switch branches, stash,
>rebase and so on from bash. When hitting [Ctrl-]F5 in gitk, the last
>highlighted commit is focused again and my HEAD is far off the screen.
>
>Is there a way to jump to the HEAD (the yellow bubble in gitk) with a
>fingertip?
>
>TIA
> Dirk
Hit the Home key. The binding for that takes you to the first commit.
End to the last (oldest) commit.
--
Pat Thoyts http://www.patthoyts.tk/
PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Gitk: shortcut to jump to the current HEAD (yellow spot)?
2011-12-22 18:26 ` Pat Thoyts
@ 2011-12-23 18:54 ` Dirk Süsserott
2011-12-24 4:22 ` Martin von Zweigbergk
0 siblings, 1 reply; 7+ messages in thread
From: Dirk Süsserott @ 2011-12-23 18:54 UTC (permalink / raw)
To: Pat Thoyts; +Cc: Git Mailing List
Am 22.12.2011 19:26 schrieb Pat Thoyts:
> Dirk Süsserott <newsletter@dirk.my1.cc> writes:
>
>> Hi!
>>
>> Does anybody know about a shortcut in gitk to "jump to the yellow spot"?
>>
>> I often use cmdline and gitk at the same time, switch branches, stash,
>> rebase and so on from bash. When hitting [Ctrl-]F5 in gitk, the last
>> highlighted commit is focused again and my HEAD is far off the screen.
>>
>> Is there a way to jump to the HEAD (the yellow bubble in gitk) with a
>> fingertip?
>>
>> TIA
>> Dirk
>
> Hit the Home key. The binding for that takes you to the first commit.
> End to the last (oldest) commit.
Hi Pat,
thank you, but I almost always run gitk with the '--all' parameter.
Actually, I have a function in my .bashrc for this:
# calls gitk from the top-level directory:
function gkup()
{
(cd "./$(git rev-parse --show-cdup)"; gitk --all "$@" &)
}
That's because gitk behaves odd (at least to me) when not run from the
top-level directory. E.g. the "touching paths" box won't find files in
the top dir if you don't prefix them with a slash. It's all relative to
the directory gitk was started in. To get predictable behavior, I wrote
this function and garnished it with '--all'.
Thus, my current HEAD is not always on the top of the history but
somewhere in between. However, typing "HEAD" (or "head" in the SHA1
field works for me.
Cheers
Dirk
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Gitk: shortcut to jump to the current HEAD (yellow spot)?
2011-12-23 18:54 ` Dirk Süsserott
@ 2011-12-24 4:22 ` Martin von Zweigbergk
2011-12-25 19:33 ` Dirk Süsserott
0 siblings, 1 reply; 7+ messages in thread
From: Martin von Zweigbergk @ 2011-12-24 4:22 UTC (permalink / raw)
To: Dirk Süsserott; +Cc: Pat Thoyts, Git Mailing List
2011/12/23 Dirk Süsserott <newsletter@dirk.my1.cc>:
>
> That's because gitk behaves odd (at least to me) when not run from the
> top-level directory. E.g. the "touching paths" box won't find files in
> the top dir if you don't prefix them with a slash.
This should be fixed in c332f44 (gitk: Fix file highlight when run in
subdirectory, 2011-04-04), which is in the current master and thus, I
believe, to be released in Git 1.7.9.
Martin
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Gitk: shortcut to jump to the current HEAD (yellow spot)?
2011-12-24 4:22 ` Martin von Zweigbergk
@ 2011-12-25 19:33 ` Dirk Süsserott
0 siblings, 0 replies; 7+ messages in thread
From: Dirk Süsserott @ 2011-12-25 19:33 UTC (permalink / raw)
To: Martin von Zweigbergk; +Cc: Pat Thoyts, Git Mailing List
Am 24.12.2011 05:22 schrieb Martin von Zweigbergk:
> 2011/12/23 Dirk Süsserott <newsletter@dirk.my1.cc>:
>>
>> That's because gitk behaves odd (at least to me) when not run from the
>> top-level directory. E.g. the "touching paths" box won't find files in
>> the top dir if you don't prefix them with a slash.
>
> This should be fixed in c332f44 (gitk: Fix file highlight when run in
> subdirectory, 2011-04-04), which is in the current master and thus, I
> believe, to be released in Git 1.7.9.
>
> Martin
Ahh, cool. I wouldn't have noticed because I'm so used to my "cd $TOP &&
gitk". I thought it was by intention because it just behaves like "git
log": When run from subdirs it doesn't know about topdir files: Assume
README.txt is in the topdir and current dir is some subdir:
$ git log -- README.txt # fails
$ git log -- ../README.txt # works
My alias (or function) was just a helper to avoid remembering where I
started gitk from.
Cheers,
Dirk
BTW, Merry X-Mas to you and all others on the list :-)
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-12-25 19:34 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-22 15:49 Gitk: shortcut to jump to the current HEAD (yellow spot)? Dirk Süsserott
2011-12-22 17:09 ` Martin von Zweigbergk
2011-12-22 17:23 ` Dirk Süsserott
2011-12-22 18:26 ` Pat Thoyts
2011-12-23 18:54 ` Dirk Süsserott
2011-12-24 4:22 ` Martin von Zweigbergk
2011-12-25 19:33 ` Dirk Süsserott
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).