Directory name completion

[Patrick O'Callaghan]

On Tue, 2011-06-21 at 15:27 -0500, Aaron Konstam wrote:
> On Tue, 2011-06-21 at 10:43 -0430, Patrick O'Callaghan wrote:
> > On Tue, 2011-06-21 at 09:21 -0400, Genes MailLists wrote:
> > > On 06/21/2011 09:07 AM, suvayu ali wrote:
> > > > On Tue, Jun 21, 2011 at 5:14 AM, Patrick O'Callaghan
> > > > <pocallaghan at gmail.com> wrote:
> > > >> However under F14 I had everything set up so that typing 'cd foob<tab>'
> > > >> would complete the name. Now under F15 this no longer works, though I
> > > >> don't recall changing anything in my Shell environment.
> > > >>
> > > > 
> > > > AFAIR, I noticed something similar with bash completions not working
> > > > after upgrading to F15. Can't recall exactly what was the problem
> > > > though, my F15 system is offline for the last month.
> > > > 
> > > 
> > >   For what its worth this works fine for me. Is it possible there are
> > > multiple matches - in that case it prints the list of matches and waits
> > > for more information from user.
> > > 
> > >   What exactly is the circumstance that it fails?
> > 
> > The circumstance that I try it and it does nothing. There is no
> > ambiguity in the prefix and typing the <tab> has no effect whatever (no
> > list of alternatives, no beep, no tab character inserted).
> > 
> > This is happening on two separate F15 installations, both being upgrades
> > from F14.
> > 
> > poc
> > 
> 
> This works for me. It seems to me probable that despite your assertion
> the files are not in your current path. Try: echo $PATH
> I assume you know the path you are in is not in the current path by
> default.

AFAIK $PATH has nothing to do with it. The appropriate variable is
$CDPATH and yes, the directory is in it.

poc