Bug 692542

Summary:	bash-completion breaks completion of dirnames in bash
Product:	[Fedora] Fedora	Reporter:	Matěj Cepl <mcepl>
Component:	bash-completion	Assignee:	Ville Skyttä <ville.skytta>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	jmontleo, mcepl, sheltren, ville.skytta
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-31 19:27:57 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 Matěj Cepl 2011-03-31 14:14:13 UTC

Description of problem:
Tab completion of a directory (not in cd, which works fine) doesn't complete correctly.

less /us<TAB>

gives

less /usr<space>

instead of

less /usr/

Version-Release number of selected component (if applicable):
bash-4.2.8-1.fc15.x86_64
bash-completion-1.3-2.fc15.noarch


How reproducible:
100%

Comment 1 Matěj Cepl 2011-03-31 14:28:24 UTC

The reason why it is not a bash issue is that when I run

conplete -r

then everything works as expected.

And rpm -V bash-completion doesn't show any other difference than what's changed by patch for bug 692548

Comment 2 Ville Skyttä 2011-03-31 19:27:57 UTC

This is almost certainly caused by acroread.sh from Adobe Reader which overrides bash-completion's _filedir() with an incompatible version.  If not, feel free to reopen this bug, but more details will be needed.

http://forums.adobe.com/thread/745833
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613326
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/716008
https://aur.archlinux.org/packages.php?ID=16980

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

Comment 3 Ville Skyttä 2011-04-10 07:40:42 UTC

*** Bug 695017 has been marked as a duplicate of this bug. ***