GNOME Bugzilla – Bug 702686
Reloading a repository moves the selected commit
Last modified: 2014-07-10 20:19:03 UTC
I do not know whether intentional or not, but: 1. Open a repository 2. Browse some commits (not the first one) 3. Press F5 Result: The cursor moves to the first commit Expected result: Reloaded history but keep the previously selected commit. In my case, it happens by mistake and it is cumbersome to find again the previous commit (there is not history of visited places). I can press Home to go to the first commit, but I need to do more work to go back when I was, specially when looking 'All commits' and having checked a branch for a new commit (it went to master).
Why do you even "Refresh" the repostiory, if your commit hasn't been changed yet? Refreshing repository means commits in the repository might have being changed, that says, the commit you were previously on is probably changed(usually caused by rebasing or someting), so there is no way to refocus on it.
If I commit on a terminal, gitg rarely detect new commits. If a file was selected, then why not keep selected that one? Likely I am working on the same file and I want to see the diff and whatnot.
I also commit on a terminal, and gitg only serves a diff purpose. What do you mean by "If a file was selected"? I thought you were saying to stay on the commit you were previously on, which as I said there is a great chance that commit was gone, but we could try to find that commit, At least for my situation, because I rebase a lot. If you were saying to stay on the same file in the file view no matter whatever commits it is, it could be done I think.
Maybe it has changed in master. In such case, close this as invalid.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.