From: johnp3 AT idt DOT net (Xyloplax)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Some things don't run under bash
Date: Sun, 06 Jul 1997 05:46:30 GMT
Organization: Damage, Inc
Lines: 17
Message-ID: <33bf30ea.51814266@news.idt.net>
References: <199707041814 DOT LAA22002 AT adit DOT ap DOT net>
NNTP-Posting-Host: ppp-51.ts-4.nyc.idt.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On Fri, 4 Jul 1997 18:14:39 GMT, Nate Eldredge <eldredge AT ap DOT net>
wrote:

>Sort of on the same thread, one thing that I would imagine is difficult for
>bash newbies (like me not long ago) is the fact that bash does *not*
>automatically search the current path for executables. You have to add a "."
>to your PATH variable.
>
>I had all sorts of problems like "Whaddaya mean, 'configure: command not
>found'!? I can see it right here!"
>
You have no idea how much time that saved and how much insight as to
just how picky unix is this provided. THANK YOU.
--
John Pavlakis
johnp3 AT idt DOT net
"You can lead a yak to water, but you can't teach an old dog to make a silk purse out of a pig in a poke." -- Opus Penguin