Re: Emacs does not listen on w32

[Lennart Borgman (gmail)]

Jason Rumney wrote:
> Lennart Borgman (gmail) wrote:
> > I do not understand what you mean here. Does the lisp thread look for 
> > new messages when it is looping? (I think it should.)
> It reads the message queue at the normal points where normal keyboard 
> input is read (not Ctrl-G, that is handled specially). You have to call 
> specific functions in your lisp loop to arrange for it to happen inside 
> your loop. You might do that if you expect your loop to take a long 
> time, but probably not if it is an infinite loop because of a bug.

Is it necessary to call those specific functions? Can't we use the same 
mechanism that is used for Ctrl-G when WM_CLOSE is recieved? (After a 
timeout of course.)


> > If it does not then we can't do any useful after a SendMessage with 
> > timeout either, or can we?
>
> If we used SendMessage, then the system would detect that we aren't 
> responding to that message after its timeout.

I see. That is a benefit, but that does not help very much if the goal 
is to give the user a chance to save data (or bring Emacs back to a 
useable state).