Subject: Warning: could not send message for past 4 hours

From: Mail Delivery Subsystem <[email-masked]>
Date: Sat, 18 Dec 1999 14:09:13 +1100 (EST)

**********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Sat, 18 Dec 1999 09:38:36 +1100 (EST)
from [email-masked] [61.8.20.208]

   ----- The following addresses had transient non-fatal errors -----
<[email-masked]>

   ----- Transcript of session follows -----
<[email-masked]>... Deferred: No route to host
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

Subject: Re: FvwmTaskBar hangs if moved
From: Chris Rankin <[email-masked]>
To: [email-masked] (Tim Phipps)
Date: Sat, 18 Dec 1999 09:32:19 +1100 (EST)

> Fix:
> 	The Alarm() signal handler has this in it:
> 
>   if (trigger_event)
>   {
>     event.xmotion.x = -1;
>     event.xmotion.y = -1;
>     event.xany.type = MotionNotify;
>     XSendEvent(dpy, win, False, EnterWindowMask, &event);
>   }

Yes, it's gross and illegal. It should also be migrated out of the
handler. The fix involves finding a place (or places) in the code to
check "trigger event" such that it will be executed as soon after the
handler returns as possible, and BEFORE the values of dpy and win
change. That's nasty.

Chris.