Bug 176790

I don't see this behaviour with bash 2.05.0(1)-release on SunOS or
3.00.16(1)-release on Suse9 (no bash-completion in either case)

In both cases the steps above produce no expansion, pressing <TAB> again shows
the files in the current working dir, not the file in the directory 'd', so
tab-completion of partially-quoted paths does not work.

I think the difference you're seeing is just due to what other files are in your
CWD.  Try:

rm -rf arena
mkdir arena
cd arena
mkdir d
touch d/f
ls d/'<TAB>

Also happens with bash-3.1.

Re: comment #2
Tim, you're right, sorry for the noise.

Reported upstream.

Upstream response:

-->
Readline understands single- and double-quoted strings and uses them
as individual words to complete.  The quotes are word breaks.  This
has been the case for a very long time.

Chet
<--

OK, try this:

mkdir -p arena/d1 arena/d2
cd arena
touch d1/f
ls d1/'<TAB>

If this starts a new word, it should expand to d1/'d and stop, instead it
expands to d1/'d1/f' which means the look up of '<TAB> finds d1/f but not d2

That's what happens on the Suse system, and also on FC4 if I uninstall
bash-completion i.e. it's a bash-completion bug and should be re-opened.

bash-completion is not part of the bash package.

Reproduced also with bash 3.1 in Rawhide.  No time to dig deeper now, but I
think upstream (ian) would be interested in hearing about this.

I tried to change this bug to bash-completion when I the bug was in that
package, but it wasn't in the dropdown.  Should I have changed the product to
Extras, submitted and tried again?

Probably, and Bugzilla would probably have noticed that the component "bash"
doesn't exist in Extras and asked you to specify a new one before letting it
proceed.  Anyway, it's already corrected.

still present in FC5's bash-completion-20060301.noarch

Still present in FC6's bash-completion-20060301-2.fc6.noarch, bumping distro
version now that FC < 5 are EOL in Extras.

REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.

still present in Fedora 7 (bash-completion-20060301-3.fc7)

This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

still present in F10

how do i re-open this?

Still present in Rawhide's 20080705-2.20090115bzr1252

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Forwarded upstream:

https://alioth.debian.org/tracker/index.php?func=detail&aid=312102&group_id=100114&atid=413095