GNU bug report logs -
#21092
25.0.50; Option `lazy-highlight-max-at-a-time' does not work
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Sun, 19 Jul 2015 13:38:02 UTC
Severity: minor
Found in version 25.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
> OK, I think I found the problem. I have something working,
> but will send it in the form of a patch in a while.
>
> Essentially, it is the isearch.el code itself that imposes, in
> a few places, not searching past (window-end) or before
> (window-start), regardless of the value of
> `isearch-lazy-highlight-max-at-a-time'. This is what needs to
> be fixed, to be (point-max) and (point-min) when
> `isearch-lazy-highlight-max-at-a-time' is nil.
>
> A more thoroughgoing fix would take into account a numeric
> value of `isearch-lazy-highlight-max-at-a-time', but I won't
> bother with that, for now.
Attached is a quick patch that seems to be OK wrt fixing
things for a nil value of `isearch-lazy-highlight-max-at-a-time'.
Please give it a try. If OK then I will update the doc and
defcustom to make clear that (for now) this works only for
nil and not for a large value.
Feel free to adjust the fix. Or to extend it to also take a
numeric value into account. But I will be happy if it is fixed
at least for nil.
[isearch-2015-08-28.patch (application/octet-stream, attachment)]
This bug report was last modified 8 years and 87 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.