Date:	Fri, 25 Aug 2000 11:29:54 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	rich AT phekda DOT freeserve DOT co DOT uk
Message-Id:	<2110-Fri25Aug2000112953+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<39A5AA58.FF9CC746@phekda.freeserve.co.uk> (message from Richard
	Dawe on Fri, 25 Aug 2000 00:06:00 +0100)
Subject:	Re: Command completion on /dev/drive-style paths
References:	<39A5AA58 DOT FF9CC746 AT phekda DOT freeserve DOT co DOT uk>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Fri, 25 Aug 2000 00:06:00 +0100
> 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.

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".

- Raw text -