Bug 23014 - set -o vi doesn't work
Summary: set -o vi doesn't work
Keywords:
Status: CLOSED DUPLICATE of bug 21222
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bash
Version: 7.0
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-30 01:35 UTC by Rene Uittenbogaard
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-30 14:23:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Rene Uittenbogaard 2000-12-30 01:35:05 UTC
when logged in with an account that has /bin/bash for a login shell, the
commands 'set -o vi' and 'set -o emacs' do not seem to work. 'set -o'
reports that the correct option has been set, but the shell doesn't respond
correctly. Using 'exec bash -o vi' solves the problem, after which 'set -o
vi' and 'set -o emacs' work correctly.

Comment 1 Bernhard Rosenkraenzer 2001-01-08 15:56:17 UTC

*** This bug has been marked as a duplicate of 21222 ***

Comment 2 Ian Mortimer 2001-01-11 03:35:03 UTC
I found a different variation of this bug.  If you put `set -o vi' in root's
.bashrc no editing
mode works when you login.  If you type `set  -o emacs' that works, but you
can't get
vi mode to work.   But if you remove the `set -o vi' from .bashrc then emacs
mode
works immediately and vi mode works after `set -o vi' from the command line.

Haven't tried this from a non-root account.


Note You need to log in before you can comment on or make changes to this bug.