Graysky's latest version works for me. Thank you.
Probably best to post a link to the actual revision that solved your problem in case I change or remove keys.zsh in the future: https://github.com/graysky2/configs/blo … ndings.zsh
]]>@op - did this solve your issue?
]]>Ah well, those 25 posts weren't entirely in vain then
Now we just need maggie to mark this solved.
]]>Just to be clear, you weren't to replace your .zshrc with those commands, but your keys.zsh (or whatever you called it). If that is what you did (and your post above doesn't sound quite right if you did), then that's all I've got... Sorry.
Mea culpa :red faced:
After replacing ~/.zsh/lib/keys.zsh with your 5 line file, everything works as expected both in X or from a TTY! Guess the question now is WTF?
]]>/home/facade/.zshrc:bindkey:9: no such keymap `menuselect'
/home/facade/.zshrc:bindkey:10: no such keymap `menuselect'
/home/facade/.zshrc:bindkey:11: no such keymap `menuselect'
/home/facade/.zshrc:bindkey:12: no such keymap `menuselect'
ease%
No arrow key functionality at all
]]># keybinds
bindkey "^[[A" history-beginning-search-backward
bindkey "^[[B" history-beginning-search-forward
bindkey "\ep" insert-last-word
bindkey "\eq" quote-line
bindkey "\ek" backward-kill-line
# use the vi navigation keys in menu completion
bindkey -M menuselect 'h' vi-backward-char
bindkey -M menuselect 'k' vi-up-line-or-history
bindkey -M menuselect 'l' vi-forward-char
bindkey -M menuselect 'j' vi-down-line-or-history
@graysky If you logged into a new TTY, and the new bind worked, then your .zshrc is being correctly sourced.
My suspicion is that it is still the way you have defined the keys (although that doesn't account for how they work as expected once you source the file from the TTY). In any event, as you won't test my hypothesis, the point is moot.
Thought I did?
@jason - I pasted your ~/.zprofile to my ~ and tried it out from the TTY... no change