Replies: 6 comments
-
Try putting |
Beta Was this translation helpful? Give feedback.
-
Closing since this is in essence a duplicate of #3435. |
Beta Was this translation helpful? Give feedback.
-
@mcornella Hey Marc, thanks for your reply. Here is some information that might help:
So, I am wondering if the behavior I mentioned above was due to the different method being called? If so, how may I override that? |
Beta Was this translation helpful? Give feedback.
-
Ok, then this is the effect of switching to viins keymap while those key bindings are put on the emacs keymap—from #5113 should be able to solve this, but in the meantime, add the correct bindkey commands to your zshrc file, after OMZ is sourced. |
Beta Was this translation helpful? Give feedback.
-
I was interested in the same thing and solution to this. I added to the end of my $ cat >> ~/.zshrc <<EOF
bindkey "^P" up-line-or-history
bindkey "^[OA" up-line-or-beginning-search
bindkey "^[[5~" up-line-or-history
bindkey "^[[A" up-line-or-history
bindkey "^N" down-line-or-history
bindkey "^[OB" down-line-or-beginning-search
bindkey "^[[6~" down-line-or-history
bindkey "^[[B" down-line-or-history
EOF |
Beta Was this translation helpful? Give feedback.
-
@vald-phoenix you are the MVP, sir, thank you. |
Beta Was this translation helpful? Give feedback.
-
Here is how it works when
vi-mode
is NOT active:This is my expected behavior where completion is performed based on the input (a.k.a. "expand" completion result)
While
vi-mode
is active:The completion does not take the input. Instead, the completion works as if nothing was typed in.
Little bit more details if anyone is interested:
up
for completion.zshrc
is underplugins
:plugins=( git zsh-syntax-highlighting zsh-autosuggestions + vi-mode )
Beta Was this translation helpful? Give feedback.
All reactions