summaryrefslogtreecommitdiff
path: root/plugins/ant
diff options
context:
space:
mode:
authorMax Bane <max.bane@gmail.com>2012-11-28 02:02:58 -0500
committerMax Bane <max.bane@gmail.com>2012-11-28 02:02:58 -0500
commit53854754e0d052c41587c7d84b9be7868f31bfe8 (patch)
treedde58a78dcfc4e7f687ff7dcedffa4b1a263e86c /plugins/ant
parentd750e7d9e3b7d04bafc93211f7db4c607ecea19b (diff)
downloadzsh-53854754e0d052c41587c7d84b9be7868f31bfe8.tar.gz
zsh-53854754e0d052c41587c7d84b9be7868f31bfe8.tar.bz2
zsh-53854754e0d052c41587c7d84b9be7868f31bfe8.zip
Revert "Fix to restore bindings after switching to vi-mode"
This reverts commit b609aa0e6c981f2039d777687cb01a84587f6edc -- this commit was a bad idea, because it makes vi-mode very difficult to use. The default `bindkey` keybindings are NOT MEANT to coexist with `bindkey -v` Vi mode; that's why `bindkey -v` clears them in the first place! Restoring all of the default keybindings after enabling Vi mode, the way the reverted commit did, causes many collisions between those default keybindings that begin with ESC and the command-mode-initiating ESC of Vi mode. See Issue 1438 of robbyrussell/oh-my-zsh. If people have custom keybindings, they should create them in their ~/.zshrc AFTER enabling the vi-mode plugin and sourcing oh-my-zsh.sh. # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # modified: plugins/vi-mode/vi-mode.plugin.zsh #
Diffstat (limited to 'plugins/ant')
0 files changed, 0 insertions, 0 deletions