X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: Re: bash 1.04.7(1)-release (i386-pc-msdosdjgpp) problems
Date: Tue, 1 Jan 2002 11:13:25 +0100
Message-ID: <000201c192ac$f35b4640$26f8e0d5@zastaixp>
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, Build 10.0.3416
In-Reply-To: <200201010418.FAA28113@father.ludd.luth.se>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
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

> I can easily make bash (version 2.04.7(1)-release
> (i386-pc-msdosdjgpp)) quit unexpectedly. I type
> "history|grep asasasas" and immediately throw myself on C-c after
> Enter.
> 
> This is done in WINDOZE 4.1 (i.e. 98) and as soon as I've done that
> WINDOZE displays a WINDOZE box saying "Finished - BASH
> <!>  This MS-DOS program has terminated. Click the Close button..."
> 
> I have a very fast CPU, an Athlon 1600+ (in case it's important).
> If you need more information, just ask!

There have been instances where typing C-c at the bash prompt
killed it, apparently depending on what the last run program was.
I'd agree with Eli: this is probably DOS rearing its ugly little
head in a way we can't avoid.