From:	pd AT kubism DOT ku DOT dk (Peter Dalgaard BSA)
Subject:	Re: Shell scripts?
27 Jan 1997 18:36:51 -0800 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<x2zpxuy9au.fsf.cygnus.gnu-win32@bush.kubism.ku.dk>
References:	<32EC4369 DOT 31DF AT omgroup DOT com> <32EC8FA8 DOT 502C AT saclink DOT csus DOT edu>
	<32ECADC0 DOT 237C AT omgroup DOT com>
Original-To:	Jan Linnell <jan DOT linnell AT omgroup DOT com>
Original-Cc:	sac24983 AT saclink DOT csus DOT edu, gnu-win32 AT cygnus DOT com
In-Reply-To:	Jan Linnell's message of Mon, 27 Jan 1997 14:29:36 +0100
X-Mailer:	Gnus v5.2.40/Emacs 19.34
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Jan Linnell <jan DOT linnell AT omgroup DOT com> writes:

> > On my computer it works both ways. Your error message suggests that you
> > do not have the current directory (.) in your path. Please verify this.
> > 
> 
> I do have . in my path, I have found a strange work-around though:
> 
> If I from the shell prompt exec another bash
> (e.g. put a exec /...../bash.exe in my .bash_profile file)
> then I can execute shell scripts "directly".

Argh. I had this problem and it disappeared, but what did I do?? Weird
stuff can and will happen if bash is not in your *DOS* path prior to
invoking it. Was that it? Your strange workaround does indicate to me
that the environment of the invoking bash might play a role.

-- 
   O__  ---- Peter Dalgaard             Blegdamsvej 3  
  c/ /'_ --- Dept. of Biostatistics     2200 Cph. N   
 (*) \(*) -- University of Copenhagen   Denmark      Ph: (+45) 35327918
~~~~~~~~~~ - (p DOT dalgaard AT biostat DOT ku DOT dk)             FAX: (+45) 35327907
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -