Re: Emacs does not listen on w32

[Lennart Borgman (gmail)]

Jason Rumney wrote:
> Lennart Borgman (gmail) wrote:
> > It looks to me there must be two bugs here:
> >
> > - Emacs not giving up cpu to windows.
>
> Since Windows NT 3.1 and 95, multitasking has been pre-emptive 
> (controlled by the OS), not co-operative (controlled by applications).
> If Windows does not allow you to use other programs when Emacs is busy, 
> that is a problem with Windows, not with Emacs. Emacs should not have to 
> "give up CPU", that is an osolete concept from the co-operative 
> multitasking days.

Yes, Stefan and you are right here of course. My bad, I did not express 
my self very good.

Stefan replied that it could be a problem with memory consumption 
instead since this can be hard for the OS to cope with. Another 
possibility is perhaps that the message queue is blocked.

> > - Emacs is not listening to OS events when it executes lisp code.
>
> You are trying to cleanly kill Emacs. That involves running Lisp code, 
> so the lisp interpreter needs to finish the infinite loop you told it to 
> execute before it gets to cleaning up and exiting.  The usual workaround 
> in such a case is to terminate Emacs uncleanly.

I would expect that the message sent to the Emacs when clicking on the 
upper left [X] would terminate any loop, just like C-g terminates a loop 
in a command.