Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!shelby!agate!usenet.ins.cwru.edu!odin!chet
From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Newsgroups: comp.unix.shell
Subject: Re: Dot in PATH?
Message-ID: <1991Feb6.154106.7067@usenet.ins.cwru.edu>
Date: 6 Feb 91 15:41:06 GMT
References: <3109@wyse.wyse.com> <1423@tau.sm.luth.se> <1991Feb6.084135.11456@wpi.WPI.EDU>
Sender: news@usenet.ins.cwru.edu
Reply-To: chet@po.CWRU.Edu
Distribution: comp
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 35
Nntp-Posting-Host: odin.ins.cwru.edu

In article <1991Feb6.084135.11456@wpi.WPI.EDU> fenn@wpi.WPI.EDU (Brian Fennell) writes:
>In article <1423@tau.sm.luth.se> d87-man@sm.luth.se (Mikael Adolfsson) writes:

>>This is not true for BASH.
>>At least version 1.05.11 allow null entries
>>without interpreting them as dot.
>
>That is definately a bug in BASH!

It certainly is.  It's also been fixed, long ago:

odin$ cd /tmp
odin$ /bin/bash -version
GNU bash, version 1.06.289 (CWRU)
odin$ PATH=:/usr/bin
odin$ cat > foo
echo this is $0
odin$ chmod +x foo
odin$ which foo
bash: which: command not found
odin$ foo
this is ./foo

>And I thought bash was suposed to be a great shell.  I am shattered.

Pull yourself up out of the gutter, man.  Bash is a great shell.  All is
right with the world once again.  :-)

Chet
-- 
Chet Ramey				``There's just no surf in
Network Services Group			  Cleveland, U.S.A. ...''
Case Western Reserve University
chet@ins.CWRU.Edu		My opinions are just those, and mine alone.