Date:	Wed, 19 Jan 2000 17:54:41 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Ian Chapman <ichapman AT nortelnetworks DOT com>
cc:	djgpp AT delorie DOT com
Subject:	RE: Bash sh
In-Reply-To:	<438D12915E64D2118AB10000F8C1C0780143A426@zcard00e.ca.nortel.com>
Message-ID:	<Pine.SUN.3.91.1000119175149.13343M-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 19 Jan 2000, Ian Chapman wrote:

> What exactly happens when the scripts do NOT run?  Error messages?  
> Crashes?  Please describe this.
> //  command not found
> 
> > However, they do run some of the time.  I think if I look at them with 
> > less after that the system seems to know what they are.
> 
> This sounds like a black magic to me.  How come viewing a file with Less 
> suddenly changes how the filesystem treats it?
> //  That's what I was asking myself.  Maybe it was a typo but I did recheck
> as I was really puzzled.
> 
> On what OS did you see this?
> // bash in a win95 dos window.  Bash was invoked as the logon shell per info
> I received fro this news group some time back.

Perhaps you were creating the script after Bash already recorded the 
contents of the directories along PATH.  Doesn't Bash have some command 
to rescan the directories?

> //  My 2nd question was should (My_prog  My_data) on line 2
> what exactly should I type get it to run.  Maybe it's to do with
> exporting the environment path to a sub shell.

Do you change PATH inside the shell?

- Raw text -