Bug 783412

Summary: bash filename completion fails
Product: [Fedora] Fedora Reporter: George R. Goffe <grgoffe>
Component: bash-completionAssignee: Ville Skyttä <ville.skytta>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: sheltren, ville.skytta
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-20 14:16:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description George R. Goffe 2012-01-20 10:35:42 UTC 
Description of problem:

bash-4.2.20-1.fc16.x86_64 fails to complete filenames for "sh -xv filen"

Version-Release number of selected component (if applicable):
bash-4.2.20-1.fc16.x86_64


How reproducible:

Always

Steps to Reproduce:
1.touch filenamecompletion
2.enter sh -xv filenamec
3.hit tab key
  
Actual results:

bash fails to complete the filename

Expected results:

"sh -xv filenamecompletion"

Additional info:

bash from ftp.gnu.org, bash-4.2.tar.gz + patches 1..20 fails to source /root/.bashrc but filename completion works; bash-4.2.20-1.fc16.x86_64 filename completion fails but source /root/.bashrc does not.
Comment 1 Ville Skyttä 2012-01-20 14:16:17 UTC 
sh completion completes *.sh filenames only.  If you want it to complete all filenames, hit Alt+/ instead of tab.
Comment 2 George R. Goffe 2012-01-20 20:49:41 UTC 
Ville,

Thanks for your response.

This is not how it used to work. Why did it change?

I have a bash at work that behaves as I'm expecting it to AND the bash I compiled from the ftp.gnu.org sources behaves the way I'm expecting it to behave.

Regards,

George...
Comment 3 Ville Skyttä 2012-01-20 22:10:41 UTC 
As of Fedora 16, the bash-completion package is installed by default.  You can remove it if you don't like it.  The version of bash you're running doesn't have anything to do with this.