Bug 23014

Summary:	set -o vi doesn't work
Product:	[Retired] Red Hat Linux	Reporter:	Rene Uittenbogaard <ruittenbogaard>
Component:	bash	Assignee:	Bernhard Rosenkraenzer <bero>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	7.0	CC:	i.mortimer
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-12-30 14:23:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.