delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | djgpp-workers AT delorie DOT com |
Date: | Thu, 28 Jun 2001 11:20:08 -0400 |
MIME-Version: | 1.0 |
Subject: | Re: bash 2.04 build failure? |
Message-ID: | <3B3B12E8.1534.5BB393@localhost> |
In-reply-to: | <CAEGKOHJKAAFPKOCLHDIGEOGCEAA.tim.van.holder@pandora.be> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 1010628154428 DOT 13433F-100000 AT is> |
X-mailer: | Pegasus Mail for Win32 (v3.12c) |
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 |
> > We've been through this before, and I know that you think dosexec should > > behave like that in general. But Mark was saying that the case > > of Bash was special, and that is what I asked about. I agree with Tim's answer to the question (darn these time zones). What I want is a flag that when turned on allows Bash to have its way. For example: int __spawn_flags; __spawn_flags |= SPAWN_FLAGS_NO_EXT_SEARCH; This would keep the default way, but allow the unix way if a programmer wants it that way. Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |