Closed Tainted-Fool closed 1 year ago
This happens because zsh-vi-mode
is lazy-loaded. This can cause some unpredictable things to happen, despite having the correct load order in your ~/.zshrc
.
The simplest solution is to turn off lazy-loading by doing:
ZVM_INIT_MODE=sourcing
Or you can also do something like:
zvm_after_init_commands=(autopair-init)
For posterity and just in case it helps someone with the same problem, setting ZVM_INIT_MODE=sourcing
didn't help, but setting zvm_after_init_commands=(autopair-init)
did.
Also it might be helpful to set AUTOPAIR_INIT_INHIBIT=1
so you don't initialize zsh-autopair twice.
@musjj and @Anomalocaridid suggested fixed my issue. Thank you very much for the help. You guys rock!
General information
Basic examination
Problem description
All my plugins were working properly until I introduced this plugin into the mix. Basically, this plugin conflicts with (zsh-autopair)[https://github.com/hlissner/zsh-autopair] . When I remove this plugin
zsh-vi-mode
,zsh-autopair
works. The autopair plugin does not get initialized if I enable this plugin.For example as soon as I press quotation mark
"
I should get another"
right next to the cursor i.e. autopair. However, when I enable this, the pair does not show up unless I runsource ~/.zshrc
or initialize the autopair withautopair-init
Reproduction steps
~/.zshrc
file:'
,"
,(
, etc.Expected behavior
Autopair to trigger as soon as you open a terminal. I don't mind initializing autopair but it should do it on its own based on the
~/.zshrc
settings. Apart from that, I am loving the plugin so far! Keep up the good work š