On Thu, May 10, 2012 at 6:40 PM, Eli Zaretskii <e...@gnu.org> wrote: >> From: Lennart Borgman <lennart.borg...@gmail.com> >> Date: Thu, 10 May 2012 14:46:01 +0200 >> Cc: help-emacs-windows@gnu.org >> >> I have a feeling that perhaps Emacs does not respond when it runs >> the init files and that makes Win7/64-bit guess that Emacs is >> dead. > > Nice theory, but it can't happen, since the Emacs message pump runs in > a separate thread. So even if the main thread is processing lots of > Lisp, the messages sent by Windows are still being received and > processed by the other thread. If this weren't so, you will have > "Emacs is not responding" each time you invoked a long-running program > via call-process.
Are you sure that there can not be any blocking calls between the threads. I am not. > And you yourself said that this didn't happen on XP. When it comes to this problem I am not quite sure. Emacs did stop responding now and then so it could actually have happened there two. > So some other factor is at work here. I still think that it could be problems with the w32 message handling.
