[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
vi mode fails if set before input
From: |
markjreed |
Subject: |
vi mode fails if set before input |
Date: |
Wed, 11 Apr 2001 16:12:58 -0400 (EDT) |
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-mandrake-linux-gnu'
-DCONF_VENDOR='mandrake' -DSHELL -DHAVE_CONFIG_H -D_FILE_OFFSET_BITS=64 -I.
-I/usr/include -I. -I./include -I./lib -I/usr/include -O3 -fomit-frame-pointer
-pipe -s -march=pentium -ffast-math -fexpensive-optimizations
uname output: Linux charm 2.2.17-21mdk #1 Thu Oct 5 13:16:08 CEST 2000 i686
unknown
Machine Type: i586-mandrake-linux-gnu
Bash Version: 2.04
Patch Level: 12
Release Status: release
Description:
If the edit mode is set to vi before the shell reads any input
(e.g. a "set -o vi" command in the .bashrc), editing does not
work; the escape key does nothing but cause the next key entered
to generate a bell.
In the most simple case, reissuing the "set -o vi" command
once readline() has been called will correct the problem.
In my actual shell environment, this is not the case; the vi
mode is gone for the lifetime of the shell process.
So there's some interaction I have not captured,
but I suspect that fixing the simple case will fix the
complex one as well.
As long as readline() is invoked at least once before vi mode is
set, the problem does not occur.
Note that the problem appears to be in readline itself, not
bash, as I have seen identical behavior in a different application
using readline 4.1.
Repeat-By:
Set vi mode editing in bashrc; start a new shell. Try to
use any command-line editing features.
- vi mode fails if set before input,
markjreed <=