You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tested with another terminal program (not applicaple)
Problem description
Some how binding CTRL+R gets overwritten when the plugin is loaded, but this is not mentioned in the readme (?).
This is especially the case when first loading the z-shell/zsh-navigation-tools
Reproduction steps
Use antidote and load first this plugin then immediately after the z-shell/zsh-navigation-tools.
CTRL+R should open up the n-history widget. But instead the normal history bck-i-search is done.
Expected behavior
CTRL+R is not overwritten or reset?
Of course the behavior can be disabled with local ZVM_INIT_MODE=sourcing when first loading this plugin.
I am just confused why this overwrite happens?
The text was updated successfully, but these errors were encountered:
Thanks for your issue, I think your problem is similar to #15 as the reason mentioned in README. You can load your specific plugin after zsh-vi-mode is initialized aspect as below.
I have a similar issue, I was using fzf plugin for the nice history search widget, after installed zvm, I find that when I do Ctrl+R in normal mode, it gives me fzf as before, but in insert mode, it gives me the primitive bck-i-search: prompt.
General information
Please report the following information as possible as you can:
Basic examination
Problem description
Some how binding
CTRL+R
gets overwritten when the plugin is loaded, but this is not mentioned in the readme (?).This is especially the case when first loading the
z-shell/zsh-navigation-tools
Reproduction steps
n-history
widget. But instead the normal historybck-i-search
is done.Expected behavior
CTRL+R is not overwritten or reset?
Of course the behavior can be disabled with
local ZVM_INIT_MODE=sourcing
when first loading this plugin.I am just confused why this overwrite happens?
The text was updated successfully, but these errors were encountered: