X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id:	<200201011736.SAA29587@father.ludd.luth.se>
Subject:	Re: bash 1.04.7(1)-release (i386-pc-msdosdjgpp) problems
In-Reply-To:	<Pine.SUN.3.91.1020101084210.20869I-100000@is> from Eli Zaretskii at "Jan 1, 2002 08:44:04 am"
To:	djgpp-workers AT delorie DOT com
Date:	Tue, 1 Jan 2002 18:36:12 +0100 (MET)
X-Mailer:	ELM [version 2.4ME+ PL54 (25)]
MIME-Version:	1.0
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

According to Eli Zaretskii:
> 
> On Tue, 1 Jan 2002, Martin Str|mberg wrote:
> 
> > 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..."
> 
> Probably some window of opportunity where C-c isn't caught and ignored.
> 
> I'm not even sure this is something Bash could reasonably fix: C-c is 
> handled specially by both DOS and COMMAND.COM, so they might do something 
> out of Bash's control.
> 
> Just don't do that...

Easier said than done. This is the easy way to reproduce it. It can
also happen anytime I press C-c. Like typing up-arrow many times, then
deciding it's not near in the history, one C-c to get a clear command
line -> crash (and this is more sane typing speed). But this only
happen very seldom, but it's madly annoying when it does.

Where are the older bashes? Like 2.03 or earlier?


Right,

						MartinS

- Raw text -