From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Fri, 29 Jun 2001 09:25:40 +0200
To:	djgpp-workers AT delorie DOT com
Subject:	Re: bash 2.04 build failure?
Message-ID:	<20010629092540.B223@lauras.lt>
Mail-Followup-To:	djgpp-workers AT delorie DOT com
References:	<CAEGKOHJKAAFPKOCLHDIOEONCEAA DOT tim DOT van DOT holder AT pandora DOT be>
Mime-Version:	1.0
In-Reply-To:	<CAEGKOHJKAAFPKOCLHDIOEONCEAA.tim.van.holder@pandora.be>
User-Agent:	Mutt/1.3.18i
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

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

IMHO we should have an env variable too - so a conscious user doesn't 
have to change the code, just relink apps, in order to change the
behaviour. And a startup flag / runtime variable is required too, so
apps, like bash, may have a reasonable default.

OTOH, I think that if we implement this, then search order should be
reverted to be unix-like again - we have more genuine DJGPP and UNIX
apps that DOS ones.

Does anyone have plans to implement it? If not, I can take it.

Laurynas
 

- Raw text -