|
From: | Lennart Borgman (gmail) |
Subject: | Re: Emacs does not listen on w32 |
Date: | Mon, 14 Apr 2008 23:02:31 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 |
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).
[Prev in Thread] | Current Thread | [Next in Thread] |