Path: utzoo!attcan!telly!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!crackers!m2c!wpi.WPI.EDU!fenn
From: fenn@wpi.WPI.EDU (Brian Fennell)
Newsgroups: comp.unix.shell
Subject: Re: Dot in PATH?
Message-ID: <1991Feb6.084135.11456@wpi.WPI.EDU>
Date: 6 Feb 91 08:41:35 GMT
References: <1991Jan28.003846.25111@bradley.bradley.edu> <3109@wyse.wyse.com> <1423@tau.sm.luth.se>
Distribution: comp
Organization: Worcester Polytechnic Institute
Lines: 22

In article <1423@tau.sm.luth.se> d87-man@sm.luth.se (Mikael Adolfsson) writes:
>bob@wyse.wyse.com (Bob McGowen x4312 dept208) writes:
>
>deleted discussion...
>
>>PATH=:/usr/lbin...<rest of path deleted>
>>    ^^
>>This is a null path entry which defautlt to dot.  You can have null
>>entries anywhere by either placing two colons together (::) or placing
>>a single colon at the beginning (as you did) or at the end.
>
>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!
Even brain-dead csh fools with "path" and leaves "PATH" in standard
format.

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

Brian Fennell == fenn@wpi.wpi.edu