GNU bug report logs - #29360
26.0; Add full-buffer choice for `isearch-lazy-highlight'

Previous Next

Full log

Message #47 received at 29360 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Juri Linkov <juri <at> linkov.net>
Cc: 29360 <at> debbugs.gnu.org
Subject: RE: bug#29360: 26.0; Add full-buffer choice for
 `isearch-lazy-highlight'
Date: Tue, 23 Oct 2018 15:51:14 -0700 (PDT)

> Bad news: when I tried to type an isearch string on a large file
> (about 1MB) after typing the first character 'e' lazy-highlighting
> became unresponsive busy highlighting all 50000 matches in that file.
> 
> Do you think we should start lazy-highlighting for the full buffer
> only when the length of the search string is more than 1 character?


Absolutely.  Like with any similar interaction in
Emacs the delay before starting should be a user
option.  Users are different, and user machines etc.
are different.

Another possibility is for the option value to be
a choice of either:

* A non-negative number of seconds (or maybe natnump)
* A cons (SIZE . DELAY), where SIZE is the buffer-size 
  threshold: no delay if the buffer is no larger than
  this, and DELAY seconds delay if greater than this.

Another possibility, to accomplish the same thing (delay
and threshold) is to have two different options:

lazy-highlight-delay - just the delay
lazy-highlight-threshold - just the size threshold

The latter approach is what I use in Icicles, for
several such settings, e.g.
`icicle-incremental-completion-delay' and
`icicle-incremental-completion-threshold'

But maybe the former approach is simpler.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.