-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Resolve conflicts between prompt/picker bindings #1792
Conversation
Currently, the picker's re-using a few bindings which are also present in the prompt. This causes some editing behaviours to not function on the picker. **Ctrl + k** and **Ctrl + j** This should kill till the end of the line on prompt, but is overridden by the picker for scrolling. Since there are redundancies (`Ctrl + p`, `Ctrl + n`), we can remove it from picker. **Ctrl + f** and **Ctrl + b** This are used by the prompt for back/forward movement. We could modify it to be Ctrl + d and Ctrl + u, to match the `vim` behaviour.
dca284d
to
e07d269
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I don't know if I use ctrl-k/-j or -p/-n on the picker but I guess we'll see, I might need to retrain my muscle memory :D
The Cc: @archseer |
Ah, I missed this PR -- I opened the original issue to add |
Currently, the picker's re-using a few bindings which are also present
in the prompt. This causes some editing behaviours to not function on
the picker.
Ctrl + k and Ctrl + j
This should kill till the end of the line on prompt, but is overridden
by the picker for scrolling. Since there are redundancies (
Ctrl + p
,Ctrl + n
), we can remove it from picker.Ctrl + f and Ctrl + b
This are used by the prompt for back/forward movement. We could modify
it to be Ctrl + d and Ctrl + u, to match the
vim
behaviour.