# Re: gitk refresh keeps showing dangling commits 2 messages from 2013-11-29 to 2013-12-04. Participants: Thibault Kruse, Gauthier Östervall. Thread: https://gitlist.dev/t/35435 ## Thibault Kruse, 2013-11-29 15:27 Subject: Re: gitk refresh keeps showing dangling commits Message-ID: URL: https://gitlist.dev/e/CAByu6UXXVRoQtFkU%2BA3E885pxVoiPdXXwXbozBP9gciD9BZMBQ%40mail.gmail.com In-Reply-To: ``` Hi, my Ubuntu saucy version of gitk is 1.8.3.2-1 I believe. I want to report what I believe is a bug. I have been using gitk for 3 years, and I use it to verify what I am doing in the shell. In the version I use now, the behavior has changed. When I do mkdir temp cd temp git init touch foo git add foo git commit -m 'foo' echo "bar" > foo git add foo git commit -m 'foo' gitk & then I see gitk showing the foo and bar commits, so far so good. Then, leaving gitk open, I do: git reset --hard HEAD~1 and in gitk, I select "Reload"(Ctrl-F5), and I still see both commits, not just commit foo. This is very annoying for me for doing rebases, as I don't care about all the dangling commits left by my rebases, and now I have to restart gitk each time to see a "clean" history. I believe "Refresh"(F5) may still display such commits, but a reload should display what I would get if I restarted gitk, which is just displaying one commit in the above case. cheers, Thibault ``` ## Gauthier Östervall, 2013-12-04 09:45 Subject: Re: gitk refresh keeps showing dangling commits Message-ID: URL: https://gitlist.dev/e/CAM8gEgg2v%2BisLEcf_rmACBLoaKL0VoA8k%3D2BpM2JAiY8wNvWuA%40mail.gmail.com In-Reply-To: ``` On Fri, Nov 29, 2013 at 4:27 PM, Thibault Kruse wrote: > and in gitk, I select "Reload"(Ctrl-F5), and I still see both commits, > not just commit foo. Do you use the menu entry Reload, or the keyboard shortcut Ctrl+F5? The shortcut was changed a while ago to Shift+F5. http://git.661346.n2.nabble.com/PATCH-gitk-avoid-Meta1-F5-td7444531.html ```