Date: Wed, 31 Mar 1999 09:27:42 +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 March 22nd
In-Reply-To: <199903302148.VAA25772@out2.ibm.net>
Message-ID: <Pine.SUN.3.91.990331092720.16213D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


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

> The configure script ran and its results appeared to be correct. The 
> only problem was that it couldn't create a file with two dots in its name.

What file with two dots?  There should be no such problems, and I
never had them.  Details, please.

> Speaking of ctrl-c, it seems Bash's signal handlers have been 
> reworked between 1.147 and 2.03. The adjustments Daisuke made to 
> handle ctrl-c will need to adjusted, but in what way I don't know yet.

Yes, Ctrl-C causes a traceback.  It would be nice if it would just
exit with non-zero status.