From xemacs-m  Sat Feb 15 22:42:23 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 WAA18555
	for <xemacs-beta@xemacs.org>; Sat, 15 Feb 1997 22:42:19 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcdcc00232; Sat, 15 Feb 1997 23:42:17 -0500 (EST)
Date: Sat, 15 Feb 1997 23:42:17 -0500 (EST)
Message-Id: <QQcdcc00232.199702160442@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: Re: set-window-redisplay-end-trigger
In-Reply-To: <m2sp2xwi8f.fsf@altair.xemacs.org>
References: <QQcdbf17019.199702152245@crystal.WonderWorks.COM>
	<m2sp2xwi8f.fsf@altair.xemacs.org>

Steven L Baur writes:
 > Kyle Jones writes:
 > 
 > > C-h f redisplay-end-trigger-functions RET
 >       ^
 >       v
 > 
 > > yields
 > 
 > >     redisplay-end-trigger-functions's value is nil
 > >       -- a simple built-in variable.
 > 
 > >     Documentation:
 > >     See `set-window-redisplay-end-trigger'.
 > 
 > > But set-window-redisplay-end-trigger is a void function.
 > 
 > Hmmm.  What's it supposed to do?

I dunno.  That's what I was trying to find out.  I think I was
looking to see if there were any Lisp-visible redisplay hooks and
ran into this variable.  Reading the doc string it looks like
something that would be useful for lazy-lock and setnu-mode, but
I'm not lobbying for it.

