Date: Thu, 28 Jun 2001 20:14:54 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Mark E." <snowball3 AT bigfoot DOT com>
Message-Id: <1438-Thu28Jun2001201453+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3B3B12E8.1534.5BB393@localhost> (snowball3@bigfoot.com)
Subject: Re: bash 2.04 build failure?
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010628154428 DOT 13433F-100000 AT is> <3B3B12E8 DOT 1534 DOT 5BB393 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: Thu, 28 Jun 2001 11:20:08 -0400
> 
> I agree with Tim's answer to the question

See my follow-ups.  If possible, I'd like to understand a bit better
the reasons for Bash being special.

> 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;

I think we should at least have a user option that controls this.