Re: [50 character or so descriptive subject here (for reference)]

[Andreas Schwab]

benchoff@vt.edu (Phil Benchoff) writes:

|> On Mon, Jan 28, 2002 at 08:47:29AM -0500, Chet Ramey wrote:
|> > > Machine Type: i586-mandrake-linux-gnu
|> > > 
|> > > Bash Version: 2.05
|> > > Patch Level: 1
|> > > Release Status: release
|> > > 
|> > > Description:
|> > >  :: on path causes cwd to be searched for executables, i.e. ::
|> > >  in the path acts like :.:
|> > 
|> > This is not a bug.  This is how Bourne-style shells have always behaved.
|> 
|> Thanks for the reply.  That is kind of an unfortunate behavior.  It
|> ended up on my path via an assortment of startup scripts that do
|> things like
|> 
|>     PATH=$PATH:/some/new/dir
|>      or
|>     PATH=/some/new/dir:$PATH

If $PATH is nonempty, then the behaviour only happens if $PATH already
contained an empty component to begin with.  So everything is correct.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."