Bug 75888

Summary: Vi-mode repeat last command (the '.' command) doesn't work
Product: [Retired] Red Hat Linux Reporter: Paul Iadonisi <pri.rhl1>
Component: bashAssignee: Tim Waugh <twaugh>
Status: CLOSED ERRATA QA Contact: Ben Levenson <benl>
Severity: low Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: ftp://ftp.gnu.org/pub/gnu/bash/bash-2.05b-patches/bash205b-002
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-10-16 14:33:42 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 Paul Iadonisi 2002-10-14 16:30:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
The dot command no longer works in bash-2.05b.  When editing a command in the
bash history, use of the dot command puts the readline library in  a strange
state where many vi bindings don't work as expected.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Run the bash shell
2.Place the shell in vi-mode editing with the 'set -o vi' command
3.Type several commands to add to the history
4.Type <ESC>k and then use k to scroll back some commands
5.Use the insert command ('i') to insert some text into a previous command
6.Type <ESC>
7.Use 'l' to move forward within the command
8.Type '.' to repeat the previous insert
	

Actual Results:  A terminal beep is heard and then various commands such as
change-word (cw) no longer work

Expected Results:  Previous editing command should work

Additional info:

This bug has been patched by the GNU project.  Patch is a available at:
ftp://ftp.gnu.org/pub/gnu/bash/bash-2.05b-patches/bash205b-002

Comment 1 Tim Waugh 2002-10-17 09:36:23 UTC
Patch applied in bash-2.05b-6.

Comment 2 Tim Waugh 2003-06-23 14:52:20 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2003-140.html