If I include "set -o vi" into any start script such as /home/myaccount/.profile /home/myaccount/.bashrc /etc/bashrc /etc/profile vi is set and
emacs is unset according to set -o
but the shell doesnt behave vi
After that I never get my vi-mode
Omitting set -o vi in any script I can get vi-mode by typing it into my interactive shell.
What can I do to get my vi-mode-shell automatically?
ps maybe not a bug but other systems I often handle behave as I assumed (set -o vi in /home/myaccount/.bashrc ... vi-mode in bash 1.14.7(1)
on rh62 and bash 2.04.0(1) on a tru64-unix.
This is fixed in 2.05-1.
I found a workaround that works beautifully for me in the gnu.bash.bug
>From: firstname.lastname@example.org (email@example.com)
>Subject: RE: Can't pre-set "set -o vi"
>The solution is amazingly simple. Just add these lines to your
> set editing-mode vi
> set keymap vi
>The distributed /etc/inputrc is configured exclusively for emacs mode,
>and to that end they've made it impossible to set it to vi mode. With
>these added lines, you can toggle between the two, and your default is
>vi mode. What could be better!