- 18 Nov, 2015 1 commit
-
-
Andrew Janke authored
The zle-line-init and zle-line-finish definitions here were broken with respect to smkx/rmkx because their "if" logic had fallthrough where it shouldn't, so the mode was left in rmkx all the time. This just removes those widgets entirely, because they're now defined (correctly) in lib/keybindings.zsh and not needed in plugins.
-
- 22 Feb, 2015 1 commit
-
-
Brian Derr authored
-
- 19 Feb, 2015 1 commit
-
-
Brian Derr authored
-
- 18 Feb, 2015 2 commits
-
-
Daniel Campoverde [alx741] authored
Allow ctrl-h, ctrl-?, ctrl-w after changes in normal mode.
-
Daniel Campoverde [alx741] authored
Allow ctrl-p, ctrl-n for history navigation while in insert mode.
-
- 04 Feb, 2015 1 commit
-
-
Gabor Marton authored
-
- 14 Mar, 2014 1 commit
-
-
Michael Hauser-Raspe authored
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).
-
- 03 Jan, 2013 1 commit
-
-
Greg Berenfield authored
-
- 02 Jan, 2013 1 commit
-
-
Greg Berenfield authored
-
- 28 Nov, 2012 1 commit
-
-
Max Bane authored
This reverts commit b609aa0e -- 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 #
-
- 02 Nov, 2012 1 commit
-
-
Jim Hester authored
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
-
- 20 Sep, 2012 1 commit
-
-
Jim Hester authored
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
-
- 01 Oct, 2010 1 commit
-
-
Robby Russell authored
Reorganizing plugins so that each plugin has it's own directory now so that any plugin-specific functions can be bundled within there.
-
- 26 Sep, 2010 1 commit
-
-
Tomas Kramar authored
-