[Top][All Lists]

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

bug#17837: 24.4.50; Search very slow

From: Eli Zaretskii
Subject: bug#17837: 24.4.50; Search very slow
Date: Tue, 24 Jun 2014 18:59:41 +0300

> Date: Tue, 24 Jun 2014 11:42:13 -0400
> From: Richard Stallman <address@hidden>
> CC: address@hidden, address@hidden
>     Anyway, you may wish to experiment with setting jit-lock-defer-time to
>     a non-nil value.  E.g., try setting it to 0.25 or 0.5 sec, and see if
>     that gives good results.
> I tried setting that to .1, and here's what happened.
> I typed C-s C-s (which searched for "honor").  It found the first
> occurrence and displayed it without fontifying that area.
> Then I typed C-f and got no response.  I suspect it had already
> started to highlight the other matches, and was fontifying the
> regions where they occur.
> The C-f was executed after 30 seconds or more.

Does anything change if you set redisplay-dont-pause to nil?

Stefan, isn't jit-lock supposed to stop and relinquish control if
input is available?  I thought it did, but I cannot find any code to
that effect.  What am I missing?

reply via email to

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