Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 155434 - Incorrect completion in quoted command substitution
Incorrect completion in quoted command substitution
Product: Fedora
Classification: Fedora
Component: bash (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-04-20 06:44 EDT by Kasper Dupont
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 3.1-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-03 04:12:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kasper Dupont 2005-04-20 06:44:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2

Description of problem:
If you attempt to use tab completion in a command substition between quotes, a space is put after directory names instead of the slash.

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

How reproducible:

Steps to Reproduce:
1. type: echo "$(cat /h
2. press tab to complete /home

Actual Results:  Shell expands the command to `echo "$(cat /home '

Expected Results:  Shell expands the command to `echo "$(cat /home/'

Additional info:

Expansion works correctly if you use either quotes or command substitiution, it even works if quotes are used inside the command substitution. Command substitution should work the same no matter which context it is used in. It is puzzling me how it is even possible to introduce a bug with exactly these symptoms, it may be a symptom of some more fundamental flaw. I'd like to keep this bug private until we know if it have any security implications.
Comment 1 Tim Waugh 2006-01-03 04:12:57 EST
Thanks for the report.  This is fixed in bash-3.1.

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