Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.windows.x
Subject: Re: getting CONTROL C  to interrupt X application
Message-ID: <2395@auspex.auspex.com>
Date: 29 Aug 89 18:32:10 GMT
References: <8908231747.AA20273@ATHENA.MIT.EDU> <525@granite.dec.com>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 12

>  I'm not sure if this is what you wanted,

If he genuinely wanted an asynchronous interrupt, it's probably not. 
The problem is that a polling strategy requires you to poll
periodically.  Such a strategy may be implementable in many
applications, and it may be implementable in his, though.

However, another problem is that any events delivered to the process
before the ^C, but not yet consumed, may be delivered to the program by
XNextEvent before the ^C event, which may also not be what he wanted. 
^C in UNIX (and, I suspect, other OSes) is not only delivered as an
asynchronous signal, but is delivered out-of-band.