I use the ^o (ctrl-o) shortcut to activate a script for lf file manager
What's strange is the shortcut works if I have activated lfcd manually within a terminal. If not, I simply see
in my terminal when I click ctrl-o.
If I disable the vi plugin the shortcut works on terminal startup perfectly.
Run lfcd to ensure it works and test the ctrl-o shortcut.
Ensure vi mode plugin is also activated.
Open a new terminal and immediately press ctrl-o.
Observe ^O error.
Disable vi mode plugin.
Open a new terminal and press ctrl-o.
Observe no issue and shortcut functions.
Expected behavior
vi plugin not to interfere with shortcuts from other plugins.
I've tried adjusting the order that things are loaded in my .zshrc and it doesn't make a difference unfortunately.
General information
Basic examination
Problem description
I use the ^o (ctrl-o) shortcut to activate a script for lf file manager What's strange is the shortcut works if I have activated lfcd manually within a terminal. If not, I simply see in my terminal when I click ctrl-o.
If I disable the vi plugin the shortcut works on terminal startup perfectly.
Reproduction steps
Expected behavior
vi plugin not to interfere with shortcuts from other plugins. I've tried adjusting the order that things are loaded in my .zshrc and it doesn't make a difference unfortunately.