Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <39A6AD74.4F94717B@phekda.freeserve.co.uk>
Date: Fri, 25 Aug 2000 18:31:32 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com, Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject: Re: Command completion on /dev/drive-style paths
References: <39A5AA58 DOT FF9CC746 AT phekda DOT freeserve DOT co DOT uk> <2110-Fri25Aug2000112953+0300-eliz AT is DOT elta DOT co DOT il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> > From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
> >
> > I noticed slightly weird command completion using bash 2.04 beta 5c.
> > If I type 'cd /dev/d' in a directory where I have files beginning with
> > 'd' (*), it completes to that name, e.g. '/dev/doc'. This behaviour is
> > wrong IMHO.
> 
> I think you shouldn't use "/dev/..." file names in interactive
> sessions at all.  It is meant to be used with Unix scripts that aren't
> ready for DOS-style file names with drive letters.

Much as I would like to avoid using /dev, I think I have to. Using
d:/[directory] doesn't seem to work, so I have to resort to
/dev/d/[directory]. Is this intentional?

> The problems you describe are expected behavior: "/dev/" gets stripped
> by _put_path, and you get files in the current directory.  If you want
> more fun like this, try "ls co" and press TAB: on some systems you
> will see a file called "con".

Thanks for the explanation.

Bye, Rich =]

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]