BJ> I'm running in console mode.  Unfortunately, I have 
 BJ> to find where to tunr off the shell's 
 BJ> interpretation of keys such as control-c and 
 BJ> control-z before I can make better use of the 
 BJ> maximus full screen editor from this setup.....
 WG>  
 WG> Hmm.. I think I'm running the console in curses raw() 
 WG> mode, which should (theoretically) disable the shell's 
 WG> interpretation of those keys. Maybe I need to take a 
 WG> closer look at that (fwiw, it was tested under curses 
 WG> (solaris), not ncurses).

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

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

Take care......

Bob Jones, 1:343/41

--- Maximus/2 3.01