Wes:

With updating to the code (Sat?) out of CVS, I now can use more of the
control keys....  Control-C no longer aborts maximus.  Unfortunately, some
of the control characters are still being interpreted (including
control-s), so the ANSI escape sequences of some keys, and various editing
commands are still not working in this reply.  I'll test control-z for
saving this message....  Unfortunately, control-z still places the job in
background.....

I'll have to look the stty stuff to get the control-s and other items
working in console mode....

Take care.....

Bob Jones, 1:343/41 (from 1:343/40)

 BJ> Iteresting.  I can attest                                          
       BJ> that the version of ncurses 
 BJ> I'm running in a terminal window in my default (CNOME) 
 BJ> x-window GUI is not disabling the shell's 
 BJ> interpretation of keyboard input.  Control-C kills the 
 BJ> app, and I loose the text I was writing.  :(   At least 
 BJ> I can recover from control Z (with an fg command).  
 BJ> Some other key strokes get eaten, making movement 
 BJ> within the full screen editor interesting..... 

 WG> I also updated the "int 24h handler" to recognize 
 WG> SIGINT/SIGTERM under UNIX the same way control-break 
 WG> and control-sysrq are handled under DOS/etc. I'm not 
 WG> sure if that made it into -303b or not; it's in version 
 WG> 1.2 of slib/brktrap.c.

 BJ> Control-break is not getting properly trapped in the 
 BJ> code I'm running.  Good to hear a version has this 
 BJ> fixed.  Hmmmm....  I should have this fixed now that I 
 BJ> did a cvs checkout for the source code and recompiled 
 BJ> from that.....  Hmmmm....  Time to try a control-c 
 BJ> again.....

--- Maximus/UNIX 3.03b