Message-Id: <200007041456.RAA10263@mailgw1.netvision.net.il>
Date: Tue, 04 Jul 2000 17:56:59 +0200
To: snowball3 AT bigfoot DOT com
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3961AE48.6825.87F40@localhost> (snowball3@bigfoot.com)
Subject: Re: DJGPP problem executing a script
References: <3961CA0E DOT 50A82A44 AT ecn DOT nl> <3961AE48 DOT 6825 DOT 87F40 AT localhost>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Mark E." <snowball3 AT bigfoot DOT com>
> Date: Tue, 4 Jul 2000 09:28:40 -0400
> 
> I did some debugging and the backslashes come from dosexec_find_on_path. When 
> searches along PATH, it copies PATH but doesn't convert backslashes to 
> forward slashes.

Is this __dosexec_find_on_path that is linked into Bash, or the one
linked into Perl (or something else)?

If it's __dosexec_find_on_path that's linked into Bash, it should have
seen forward slashes in PATH, since stock djgpp.env arranges for that.
Unless bash.exe and/or sh.exe are renamed, that is.

> So perhaps the solution/workaround is instead to have dosexec_find_on_path 
> always return slashes.

I think this would be too dangerous: __dosexec_find_on_path might be
used with programs that don't grok forward slashes, such as
COMMAND.COM.

I think if we need to solve a local problem with scripts, it's
sufficient to solve it locally in script_exec.