Inconsistent cursor behavior during staging #1028
Comments
koutcher
added a commit
to koutcher/tig
that referenced
this issue
May 15, 2022
In the status view, when the `Changes to be committed` section is empty, a line with `(no files)` is inserted. This line disappears when the fist file is staged, this has to be taken into account for the cursor position. Fixes jonas#842, jonas#1028
koutcher
added a commit
to koutcher/tig
that referenced
this issue
May 15, 2022
In the status view, when the `Changes to be committed` section is empty, a line with `(no files)` is inserted. This line disappears when the first file is staged, this has to be taken into account for the cursor position. Fixes jonas#842, jonas#1028
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! I've discovered that if I stage a file when the index is empty, the cursor goes down. For example, after staging
statusthe cursor moves down toinit.vim:However, if I stage a file when the index is not empty, the cursor goes up. For example, after staging
init.vimthe cursor moves up totmux-sessionist:It's a bit confusing, is this behavior intended? I think a more friendly way would be always moving the cursor down on staging unless it's the last entry in the group (staged or untracked files).
I see this behavior on tig v2.3.0 and on the master branch.
The text was updated successfully, but these errors were encountered: