Dot in PATH?
Brian Fennell
fenn at wpi.WPI.EDU
Wed Feb 6 19:41:35 AEST 1991
In article <1423 at tau.sm.luth.se> d87-man at sm.luth.se (Mikael Adolfsson) writes:
>bob at 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 at wpi.wpi.edu
More information about the Comp.unix.shell
mailing list