[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: isearch-lazy-highlight-initial-delay

From: Eli Zaretskii
Subject: Re: isearch-lazy-highlight-initial-delay
Date: Fri, 13 Oct 2000 13:36:49 +0200

> 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).

In all of those places, the value of baud_rate is compared agains the
magic value of 2400.  In addition, scroll.c's computation of the
update cost depends on the value of baud_rate.

This is what I had in mind when I wrote the above paragraph.  However,
I never fully understood the details of those computations, so perhaps
I'm barking the wrong tree here ;-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]