Sender: rich AT phekda DOT freeserve DOT co DOT uk Message-ID: <39A5AA58.FF9CC746@phekda.freeserve.co.uk> Date: Fri, 25 Aug 2000 00:06:00 +0100 From: Richard Dawe 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 Subject: Command completion on /dev/drive-style paths Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. 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've actually only noticed this with directories, but I didn't try completing with regular files. [ Actually, the drive that I tried it on has an empty /dev directory. ] [ I wonder if this confuses bash? ] This seems like a nasty problem to fix, since you don't really want to have to tell bash what "devices" are understood by DJGPP - e.g. /dev/env, /dev/c, /dev/d - to allow completion. OTOH it seems sensible to make /dev/d complete to /dev/d/ . I imagine that people wanting to use /dev/env will type in the whole of /dev/env, rather than completing /dev/e or /dev/en. But what to do with /dev/env/DJ - complete it to DJDIR. Ugh. If I'm barking up the wrong tree here, please tell me. Thanks, bye, Rich =] -- Richard Dawe [ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]