Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!think.com!mintaka!bloom-beacon!eru!hagbard!lunic!my!luth!d87-man
From: d87-man@sm.luth.se (Mikael Adolfsson)
Newsgroups: comp.unix.shell
Subject: Re: Dot in PATH?
Message-ID: <1423@tau.sm.luth.se>
Date: 6 Feb 91 05:16:49 GMT
References: <1991Jan24.203423.25084@ux1.cso.uiuc.edu> <1991Jan24.221552.5906@bradley.bradley.edu> <5528@auspex.auspex.com> <1991Jan28.003846.25111@bradley.bradley.edu> <3109@wyse.wyse.com>
Distribution: comp
Organization: University of Lulea, Sweden
Lines: 17

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.

-- 
Mikael Adolfsson            # d87-man@sm.luth.se
University of Lulea, Sweden # ...{uunet,mcsun}!sunic!sm.luth.se!d87-man