From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: Re: bash 2.04 build failure?
Date: Thu, 28 Jun 2001 21:55:08 +0200
Message-ID: <CAEGKOHJKAAFPKOCLHDIOEONCEAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20010628184328.A205@lauras.lt>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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

> 4) In this case IMO a new startup flag is the best solution.

A startup flag is good for setting the default, but this should
really be configurable at run-time (say, a __dosexec_search_mode
variable).  That way bash can have, say, 'set +commandcomstyleexec'
or an option in _inputrc to switch between modes.  I'd want a
change to the behaviour an app requests to be a conscious user
choice; having an envvar that is checked by libc doesn't feel
right.