🚀 go-pugleaf

    Does anybody know how to get control of the ^C handling?  I
    would like to find some way to prevent my program from getting
    killed without giving it a chance to clean up.  (It doesn't
    seem possible to keep a conin() request pending all the time,
    because, for instance, when you are in the middle of a long
    write() to a file you are sensitive to being killed).  Clearly
    one should just not type ^C, but I would like to make my software
    "idiot proof".

I had a similar problem with ^Q/^S when I wrote a terminal emulator
-- sometimes they would be passed through to my program and sometimes
they would be interpreted by TOS.  My advice from Atari was to avoid
the GEMDOS conin()/conout() calls altogether and to use the BIOS
calls directly.  I did that and the problem went away.  But even
though the problem was only with keyboard input, it seemed to be
necessary to avoid conout() as well, for it interacts in mysterious
ways with conin().

--Mike Fischer
-------