Re: isearch-lazy-highlight-initial-delay

[Gerd Moellmann]

"Eli Zaretskii" <address@hidden> writes:

> > Date: Fri, 13 Oct 2000 10:59:36 +0200 (CEST)
> > From: Gerd Moellmann <address@hidden>
> > 
> > > We could change these values to something less ``pathetic'', but I'm not 
> > > sure how much of the knowledge about these values is hard-wired in the 
> > > code which decides when to redisplay a screen portion and when to use 
> > > direct display manipulations.
> > 
> > I don't think there's anything in redisplay on X depending on baud
> > rates.
> 
> Perhaps I'm missing something, but I see bad_rate being used in
> the functions `update_window', `update_frame_1', and `scrolling' (all
> on dispnew.c), and in several places on scroll.c and term.c (the
> latter probably irrelevant to X).

Only update_window is used on X.  In this function, baud_rate is
currently used to determine when to check for pending input (every N
lines).  That could as well be replaced with a hard-coded constant
like every 3rd line or whatever.