Date:	Mon, 11 Jan 1999 18:41:39 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
cc:	Stuart Hall <fprintf AT iname DOT com>, djgpp AT delorie DOT com, robert DOT hoehne AT gmx DOT net
Subject:	Re: Weird RHIDE problem found - /* at end of comments causes pro
In-Reply-To:	<m0zziuw-000S2QC@inti.gov.ar>
Message-ID:	<Pine.SUN.3.91.990111183756.7632F-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Sun, 10 Jan 1999, Salvador Eduardo Tropea (SET) wrote:

> One interesting thing: Robert should implement an autosave feature when RHIDE 
> gets a SIGSEGV.

Here's an idea for another life-saver: install a handler for
SIGINT/SIGQUIT, and if the user presses the appropriate key twice before
RHIDE has a chance to return to the top level and clear the interrupt
condition, auto-save and exit (after asking the user if they really meant
that). 

Why?  Because this way you give the user an escape out of cases when 
RHIDE is stuck in some endless loop (e.g., some buggy user extension). 

- Raw text -