Date: Mon, 12 Mar 2001 10:17:27 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: RE: Fetish.pm band-aid (Fileutils testsuite)
In-Reply-To: <3AABA039.17007.33CAA6@localhost>
Message-ID: <Pine.SUN.3.91.1010312101709.24860C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Sun, 11 Mar 2001, Mark E. wrote:

> > # This is REQUIRED: using simply "/bin/(ba)sh" will NOT work (m4 needs this
> > # to be a full path with executable suffix)
> > SHELL=/dev/env/DJDIR/bin/bash.exe
> > CONFIG_SHELL=$SHELL
> 
> For a long term solution, what about enhancing system() to better handle 
> SHELL so this code can go away someday?

What enhancement did you have in mind, specifically?  I think we need
to be very careful about this, given the blissful way DOS will invoke
any file if you tell it.

(At the time the current limited support was written, the Bash
distribution didn't even include sh.exe.)