Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always/unconditionally select _next_ item in staging list after action #842

Closed
npdbharris opened this issue Jun 19, 2018 · 0 comments
Closed

Comments

@npdbharris
Copy link

npdbharris commented Jun 19, 2018

So with a console app, when dealing with a list like tig's staging list, I'd expect to be able to scroll to the first item I care about and then perform an action and have the next item selected. Items we care about tend to be clustered together in lists.

For instance if I have 10 files I don't care about followed by 10 files I want to stage/add, it's convenient to be able to scroll to item 11 and then hit u 10 times. Sadly, right now, when I press u the item above ends up being the next one focused, meaning that instead of hitting uuuuuuuuuu I end up doing something like uujujujuuujuj.

(Right now I end up scrolling to roughly the middle of the list of things I care about and then hitting u for a while until I need to reposition to the middle of the remaining items and repeat.)

Clearly this is just a usability thing, not a serious bug :)

Thanks,

Dave

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant