Commit graph

11 commits

Author SHA1 Message Date
Daniel Campoverde [alx741]
33900dfd32 PLUGINS: vi-mode: allow ctrl-h, ctrl-?, ctrl-w for char and word deletion
Allow ctrl-h, ctrl-?, ctrl-w after changes in normal mode.
2015-02-18 14:29:44 -05:00
Daniel Campoverde [alx741]
099246dd9e PLUGINS: vi-mode: allow ctrl-p, ctrl-n for history navigation
Allow ctrl-p, ctrl-n for history navigation while in insert mode.
2015-02-18 14:25:15 -05:00
Gabor Marton
7de44dbdb7 Added trapwinch to vi-mode plugin. 2015-02-04 12:56:58 +01:00
Michael Hauser-Raspe
9e90bf0f23 Added v as a keybinding to edit-command-line
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).
2014-03-14 10:14:47 +00:00
Greg Berenfield
93c90a6bf5 Fix the fix for Issue #1479 2013-01-02 19:14:57 -05:00
Greg Berenfield
003dd8f4b6 fix for Issue 1479 2013-01-02 16:20:22 -05:00
Robby Russell
3199d2ed8d Merge pull request #1387 from jimhester/vi-mode-patch
Fixes for vi-mode terminal overwriting bugs
2012-12-04 06:34:02 -08:00
Max Bane
53854754e0 Revert "Fix to restore bindings after switching to vi-mode"
This reverts commit b609aa0e6c -- 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-28 02:02:58 -05:00
Jim Hester
4e513d72b9 Fixes for vi-mode terminal overwriting bugs
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-11-02 11:06:32 -04:00
Jim Hester
b609aa0e6c Fix to restore bindings after switching to vi-mode
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
2012-09-20 08:03:09 -04:00
Robby Russell
26d97a9355 Reorganizing plugins so that each plugin has it's own directory now so that any plugin-specific functions can be bundled within there. 2010-09-30 21:34:06 -07:00
Renamed from plugins/vi-mode.plugin.zsh (Browse further)