[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

VI Editing Mode goes bad

From: Tim Maher
Subject: VI Editing Mode goes bad
Date: Mon, 12 May 2003 14:43:37 -0700
User-agent: Mutt/

Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux
Compiler: gcc -I/usr/src/packages/BUILD/bash-2.05b 
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
-DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i586-suse-linux' -DCONF_VENDOR='suse' 
-DSHELL -DHAVE_CONFIG_H  -I.  -I. -I./include -I./lib  -O2 -march=i586 
-mcpu=i686 -fmessage-length=0 -D_GNU_SOURCE -Wall -pipe -g
uname output: Linux guru 2.4.19-4GB #4 Tue Apr 22 19:04:32 PDT 2003 i686 unknown
Machine Type: i586-suse-linux

Bash Version: 2.05b
Patch Level: 0
Release Status: release

    After a while of working perfectly well, the vi-editing mode stops
    processing certain commands correctly. For example, "cw" doesn't change
    a word anymore, it ignores the "c", and then jumps forward by a word.
    "r" no longer changes the indicated character to the newly typed input,
    it changes the indicated character to an "n". (It's always an n).

    I've also occasionally seen a message approximately like the following,
    only when issuing "pwd" commands:

    write failed - SUCCESS

    And then the pwd output shows up.
    (and this happens on a real physical file system; no NFS or anything).

        Just using vi editing mode for a while.

    Running set -o emacs, followed by set -o vi doesn't change anything.
    Starting a fresh instance of bash does fix the problems, but after a
    while they show up again.

    In other words, I don't have a fix!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]