-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keys that autopair use should be able to perform their original actions after this plugin loaded #14
Comments
Alright, a more generalized solution is in place. Let me know if it gives you any trouble. |
Commit a01f074 introducing a new error. It breaks the zsh-syntax-highlighting plugin and its some features are not working correctly. Everything is okay under b486f0d. By the way, your solution isn't working even if we ignore this error. I write |
I found the problem and pushed a fix. Let me know if it gives you trouble! |
Well, I have still the same problem. I can confirm I am on e73053d. |
I don't want to derail the plugin development, but may the features be developed in separate branches, rather then in master? |
@z0rc I agree with that. |
Agreed. Sorry, should've done that from the start. I've effectively reset master to b0a995a and moved this feature to the |
Also, I wouldn't force push if I were you. Now, probably someone dealing with their weird looking git history and wondering what went wrong. There is safe alternative for that. |
I apologize for any trouble, but I understand the pitfalls. Also, In any case, your feature is now in |
Okay here's my report with this lines in my config. bindkey -M viins '^?' backward-kill-word
source "$ZDOTDIR/plugins/zsh-autopair/autopair.zsh" In In |
zsh-autopair overrides some existing keys like
"
,'
and such. Those keys can't be used with their original behaviour after zsh-autopair sourced if users have existing widgets for that.Recently, owner of this plugin added two fallback for
(Space) keys but apparently more general solution needed.
^?
(Backspace) andThe text was updated successfully, but these errors were encountered: