-
Notifications
You must be signed in to change notification settings - Fork 13
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
Make hide_confirm the default in select_multiple #9
Comments
My reasoning for this was: It is (in my opinion) more intuitive to have Concerning redundancy: as requested on Reddit I wanted to add vim shortcuts that (for better or worse) are used by many people and supported by many interfaces. What do you think? |
To add on to what Kamik423 said, if you don't want |
I don't think users that are used to graphical UI are the main concern here. It is for terminal interactions, and in the terminal world, you are used to press I don't think many users that haven't used a terminal are coming across this. Lastly, I disagree that a confirm button is more straightforward. The great strength of user interfaces with keybindings is that the actions are just one key away. With the confirm button, they are potentially very far away, as a user may be prompted with a long list, ticks an item at the top and has then to scroll all the way down to confirm his actions. @dherrada My concern was that this should be the default option ;) |
One key should represent one action, and having the tick action bound to
ENTER
andSPACE
is redundant, plus it is a few extra steps to confirm input.Selecting with
SPACE
and confirming withENTER
is more intuitive and faster, so i think this should be the default option.The text was updated successfully, but these errors were encountered: