From xemacs-m  Sat Apr 12 16:49:05 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA22572
	for <xemacs-beta@xemacs.org>; Sat, 12 Apr 1997 16:49:04 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQckzv19188; Sat, 12 Apr 1997 17:49:03 -0400 (EDT)
Date: Sat, 12 Apr 1997 17:49:03 -0400 (EDT)
Message-Id: <QQckzv19188.199704122149@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: 20.1b14 time display broken?
In-Reply-To: <E0wFlUX-0004Fm-00@neal.ctd.comsat.com>
References: <E0wFlUX-0004Fm-00@neal.ctd.comsat.com>
X-Mailer: VM 6.25 under 19.15 XEmacs Lucid
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Neal Becker writes:
 > 20.1b14 hpux9.05.  I don't know why, but the digital clock display has 
 > stopped.  
 > 
 > >date
 > Fri Apr 11 14:51:33 EDT 1997
 > 
 > but the clock says 2:14.
 > 
 > I *could* maybe have killed it by fooling with customize.  What
 > variables should I check?
 > 
 > Also I notice that font lock isn't turned on by default when I visit a 
 > c++ file.  Did something change?

The itimer code hasn't been changed recently.  My guess is that
a C-g hit the timer driver at the wrong instant and stopped the
system.  I found a race window in itimer.el where it could
happen.  I've changed the code to remove this window.  To test
it, I started a bunch of timers and leaned on C-g for a while.
The timer system kept running, so I declare it fixed... until
your clock stops again.

