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

how to write config.nu to make a new keybinding to go from vi_normal to vi_insert #815

Open
scubacabra opened this issue Aug 9, 2024 · 3 comments
Labels
question Further information is requested

Comments

@scubacabra
Copy link

Question

i use colmak-dh for my keyboard layout

i bound the keys on my home row m | n | e | i to left | down | up | right

everything works great but i lost how to go into vi_insert from vi_normal (it is i by default)?

i am on a mac, so i had karabiner remap Ctrl + Space to send an Insert keypress, hoping that would work. I can see that Insert is sent from keybindings listen but it does not switch to vi_insert -- it stays on vi_normal

from perusing some issues it seems that this is hardcoded in reedline, correct?

is this something i will have to ask over there to see if they can fix it upstream or is there another way to configure it in the config.nu file?

Additional context and details

nushell version: 0.96.1

@scubacabra scubacabra added the question Further information is requested label Aug 9, 2024
@fdncred
Copy link
Collaborator

fdncred commented Aug 10, 2024

I think it's hard coded

Some('i') => {
let _ = input.next();
Some(Command::EnterViInsert)
}
Some('a') => {

@scubacabra
Copy link
Author

thanks for pointing me to the file, i will ask them about adding the Insert key to trigger the switch to vi_insert

@fdncred fdncred reopened this Aug 10, 2024
@fdncred
Copy link
Collaborator

fdncred commented Aug 10, 2024

I can just move it to the reedline repo.

@fdncred fdncred transferred this issue from nushell/nushell Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants