Keybindings for prev- and next-char

Keybindings for prev- and next-char

[Chris Johnson]

I am using the viins keymap, but my escape key doesn't appear to bringing me
into vi-cmd-mode.  In fact,

   bindkey "^[" beep

doesn't even seem to register the key to the beep.  I'm using zsh 4.0.4 on
Mac OS 10.2.  Any ideas?

-- 
Chris Johnson
cjohnson@cs.utk.edu
http://www.cs.utk.edu/~cjohnson

Re: Keybindings for prev- and next-char

[DervishD]

    Hi Chris :)

 * Chris Johnson <cjohnson@cs.utk.edu> dixit:
> I am using the viins keymap, but my escape key doesn't appear to bringing me
> into vi-cmd-mode.  In fact,
> 
>    bindkey "^[" beep
> 
> doesn't even seem to register the key to the beep.  I'm using zsh 4.0.4 on
> Mac OS 10.2.  Any ideas?

    Could you please post the output of bindkey for the viins and
vicmd keymaps? I think that you may be having problems with the
selected keymap.

    Here your bindkey above works perfectly. If you don't hear a
beep, look if 'no_beep' option is set.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/

Re: Keybindings for prev- and next-char

[Chris Johnson]

DervishD sent me the following 0.7K:

> > I am using the viins keymap, but my escape key doesn't appear to bringing me
> > into vi-cmd-mode.  In fact,
> > 
> >    bindkey "^[" beep
> > 
> > doesn't even seem to register the key to the beep.  I'm using zsh 4.0.4 on
> > Mac OS 10.2.  Any ideas?
> 
>     Could you please post the output of bindkey for the viins and
> vicmd keymaps? I think that you may be having problems with the
> selected keymap.
> 
>     Here your bindkey above works perfectly. If you don't hear a
> beep, look if 'no_beep' option is set.

I made sure to setopt beep because I have no_beep in my .zshrc file.
However, after making some changes I sourced .zshrc and reverted back!
Sorry.  I realized this problem last night, after I had shut my machine down
and was lying safely in bed.

Upon returning to it, I found that ^[ was not bound to anything.  So,

   bindkey "^[" vi-cmd-mode

was all I needed.  Initially I had

   bindkey -M viins "^[" vi-cmd-mode

but upon closer inspection it appears that viins isn't really my keymap.
I've been using emacs without realizing it.  :(  However, EDITOR and VISUAL
are both set to vi -- in my .zshrc file.  Does it matter where these are
set?  The main page checks these "when the shell starts up."

-- 
Chris Johnson
cjohnson@cs.utk.edu
http://www.cs.utk.edu/~cjohnson

Re: Keybindings for prev- and next-char

[DervishD]

    Hi Chris :)

 * Chris Johnson <cjohnson@cs.utk.edu> dixit:
> DervishD sent me the following 0.7K:

    XDDDD, very funny attribution XD
 
> Upon returning to it, I found that ^[ was not bound to anything.  So,
> 
>    bindkey "^[" vi-cmd-mode
> 
> was all I needed.  Initially I had
> 
>    bindkey -M viins "^[" vi-cmd-mode
> 
> but upon closer inspection it appears that viins isn't really my keymap.

    Oh :(( Well, that seems to be solved :)

> However, EDITOR and VISUAL are both set to vi -- in my .zshrc file. 
> Does it matter where these are set?  The main page checks these
> "when the shell starts up."

    I don't have the slightest idea: I use my own keymap, made from
scratch. I even delete vi??? and emacs keymaps, so I've never find
which keymap was on by default :?

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/

Re: Keybindings for prev- and next-char

[Bart Schaefer]

On Sat, 6 Nov 2004, Chris Johnson wrote:

> I've been using emacs without realizing it.  :( However, EDITOR and 
> VISUAL are both set to vi -- in my .zshrc file.  Does it matter where 
> these are set?  The main page checks these "when the shell starts up."

They're checked when the zsh/zle module is loaded.  That means they have
to be set before the first time you invoke a bindkey, zle, or completion-
related builtin, because any of those will autoload zle.

Some Linux distributions (and possibly other pre-packagings of zsh) have 
"bindkey -e" or the like in their /etc/z* files, which of course cause the 
settings of EDITOR and VISUAL to be ignored.  You're best off putting an 
explicit "bindkey -v" somewhere.