From: <pgf AT cayman DOT com> (Paul Fox)
Subject: suppressing ctrl-c
Organization: Kaleida Labs, Inc.
Originator: daemon AT talisman DOT kaleida DOT com
Date: 26 Jan 94 22:43:28 GMT
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Reply-To: djgpp AT sun DOT soe DOT clarkson DOT edu



hi -- 
	i'm porting a text editor to djgpp.  error handling is obviously
	pretty important.

	i've figured out how to suppress ctrl-break, using the 
	go32...ctrl_break() functions.  and i think i've got critical
	errors licked (thanks, btw, to whoever sent me those code
	fragments...  they worked fine).

	but i still can't figure out how to suppress ctrl-c.  if i have
	a read pending, i _don't_ get killed.  if i _don't_ have a read
	pending, i _do_ get killed.  i've tried a setmode(0, O_BINARY),
	thinking that might help, to no avail.

	i even tried duping the code that implements the 
	go32_want_ctrl_break() and go32_was_ctrl_break_hit(), and created
	a want_ctrl_c()/was_ctrl_c_hit() pair, that hooks into the ctrl-c
	interrupt.  that didn't work either.  should it have?

	i'm about out of ideas...

	paul



---------------------
    paul fox, pgf AT cayman DOT com (cayman systems inc. cambr^H^H^H^H^Hwoburn, ma)
    	home: pgf AT foxharp DOT boston DOT ma DOT us (arlington, ma)