Re: [h-e-w] Workarounds for emacs on Windows 7

[Lennart Borgman]

On Thu, May 10, 2012 at 3:06 PM, Gary Oberbrunner <address@hidden> wrote:
>
>
> ----- Original Message -----
>> From: "Lennart Borgman" <address@hidden>
>> To: "Gary Oberbrunner" <address@hidden>
>> Cc: address@hidden
>> Sent: Thursday, May 10, 2012 8:46:01 AM
>> Subject: Re: [h-e-w] Workarounds for emacs on Windows 7
>>
>> On Thu, May 10, 2012 at 2:42 PM, Gary Oberbrunner <address@hidden>
>> wrote:
>> >
>> >
>> > ----- Original Message -----
>> >> From: "Lennart Borgman" <address@hidden>
>> >
>> >> Could you perhaps try this and see if Emacs hangs sometimes (as it
>> >> does for me with my one year old build, with my patches and my
>> >> build
>> >> tools):
>> >>
>> >> Start Emacs, but immediately switch to another maximized
>> >> application.
>> >> Then a rather long time afterward (maybe ten minutes, I do not
>> >> know)
>> >> switch back to Emacs.
>> >
>> > How can I live without Emacs for 10 minutes?! :-)
>>
>> ;-)
>>
>> > I'll try this and let you know.  I assume I should do it with
>> > runemacs -Q?
>>
>> No, please do it with your normal init files.
>
> Just tried it, and have no problem here.  My emacs was sitting under my 
> Chrome browser window for a long time (5+ minutes?), and when I finally 
> switched back to it just now it was as responsive as ever.  I'll try it again 
> at lunch, but based on this test I don't expect it to fail.


Thanks for testing, Gary. It does not happen every time, though.

I wonder if anyone here knows how long the timeout must be for Win7/64
to assume an application to be dead? (It is just not simply repsonding
as you can see in the task list sometimes. There is a popup from
win7/64 saying something that I can't remember right now. If you click
it then Emacs will close. Not if, when. There is no alternative.)