Date:	Wed, 10 Mar 1999 10:46:11 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT usa DOT net>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Bash 2.03 updated
In-Reply-To:	<199903091643.QAA133130@out5.ibm.net>
Message-ID:	<Pine.SUN.3.91.990310104502.10442H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 9 Mar 1999, Mark E. wrote:

> It does now. I didn't have a chance to switch to libc's malloc and 
> produce an optimized build. I could do it today, but I'd rather take that 
> time to make a snowman before the snow we got last night melts.

Sorry, I didn't mean to rush you, I just wanted to be sure when can I
download the corrected version.  I'm working on several pretest
versions of GNU packages during the last weeks, and I'd like to make
sure that the configure and build procedure there will work with the
new Bash as well as the old.

Please also tell when there's an optimized version available for
downloading.  Thanks.

> BTW, I found a non-critical problem. When you start one instance of 
> Bash, by default the prompt is 'bash-2.03$'. But if I type 'bash' to start 
> another instance of Bash, I get 'bash.exe-2.03$'.

I saw that a long time ago, but chose not to report it, because I,
too, think it's not too important.

I'm guessing that you dropped the .exe suffux by using the crt0 flag,
as I suggested, right?  If so, then you should know that the startup
code bypasses the fragment which does all this magic if the program
got arguments via the !proxy method (i.e. from another DJGPP program).
This is a known thing; DJGPP has been working like that since the days
of v1.x, but it was left alone during v2.01 testing.

So if you really want to drop the .exe, you need to do it explicitly
inside Bash sources.

- Raw text -