summaryrefslogtreecommitdiff
path: root/plugins/vi-mode
AgeCommit message (Collapse)Author
2015-09-23Update README.mdAlexander Frolov
2015-06-12Plugins: vi-mode: Add first README fileDaniel Campoverde [alx741]
2015-02-22Merge pull request #3610 from bderrly/zle-active-checkRobby Russell
Verify zle is active before trying to reset-prompt.
2015-02-21Shorten the zle check and reset-prompt into one line.Brian Derr
2015-02-19Verify zle is active before trying to reset-prompt.Brian Derr
2015-02-18PLUGINS: vi-mode: allow ctrl-h, ctrl-?, ctrl-w for char and word deletionDaniel Campoverde [alx741]
Allow ctrl-h, ctrl-?, ctrl-w after changes in normal mode.
2015-02-18PLUGINS: vi-mode: allow ctrl-p, ctrl-n for history navigationDaniel Campoverde [alx741]
Allow ctrl-p, ctrl-n for history navigation while in insert mode.
2015-02-04Added trapwinch to vi-mode plugin.Gabor Marton
2014-03-14Added v as a keybinding to edit-command-lineMichael Hauser-Raspe
taken from [here](http://www.zsh.org/mla/users/2008/msg01013.html) We want pressing v in command mode to take us to an editor (defined by the $VISUAL or $EDITOR variable or vi) to edit the current contents of the command line which (I believe) is a standard feature of bash vi-mode or other readline prompts (see [here](http://www.catonmat.net/download/bash-vi-editing-mode-cheat-sheet.pdf) and [here](http://www.catonmat.net/blog/bash-vi-editing-mode-cheat-sheet/) for source).
2013-01-02Fix the fix for Issue #1479Greg Berenfield
2013-01-02fix for Issue 1479Greg Berenfield
2012-12-04Merge pull request #1387 from jimhester/vi-mode-patchRobby Russell
Fixes for vi-mode terminal overwriting bugs
2012-11-28Revert "Fix to restore bindings after switching to vi-mode"Max Bane
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 #
2012-11-02Fixes for vi-mode terminal overwriting bugsJim Hester
fixes #387 and https://github.com/robbyrussell/oh-my-zsh/pull/1321#issuecomment-9959540 and other problems of prompt overwriting when people did not realize that it was vi mode causing the problem. Hat tip to sorin ionescu, as I took this code from prezto
2012-09-20Fix to restore bindings after switching to vi-modeJim Hester
the vi-mode plugin destroys any bindings made before it is sourced due to the 'bindkey -v' call to switch to using vi-mode. This patch saves the bindings before invoking 'bindkey -v' then rebinds them afterwards, this fixes a number of outstanding issues due to people using vi-mode and having things in oh-my-zsh break due to the bindings being destroyed
2010-09-30Reorganizing plugins so that each plugin has it's own directory now so that ↵Robby Russell
any plugin-specific functions can be bundled within there.