From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 25751@debbugs.gnu.org, antoine.levitt@gmail.com
Subject: bug#25751: Query replace lazy highlighting
Date: Mon, 20 Feb 2017 02:30:06 +0200 [thread overview]
Message-ID: <87fuj9k8px.fsf@localhost> (raw)
In-Reply-To: <06b2d640-2239-49cb-bb01-0f2f1e1bbf8e@default> (Drew Adams's message of "Sat, 18 Feb 2017 15:51:59 -0800 (PST)")
>> > You could still leave the "lazy" part, if you both remove and re-add
>> > the overlays after the idle delay. IOW, the important thing is not to
>> > have redisplay between removal and addition of the highlight.
>>
>> That's an option too, and here is the tested patch (it sets
>> lazy-highlight-max-at-a-time to nil to avoid redisplay between
>> lazy iterations):
>
> How does this relate to what has been discussed so far in bug #21092?
I'm sorry to say that, but setting lazy-highlight-max-at-a-time to nil
in the patch here in bug#25751 is a better way to avoid flicker
than highlighting all matches in the buffer as it was discussed
in bug#21092.
I believe that modern hardware can quickly highlight all matches
on the screen in one loop without a noticeable delay. But highlighting
matches in the whole buffer is another thing. Could you try to see
how fast this could be by trying to highlight a single character
in a large buffer, e.g. with ‘M-x highlight-regexp RET a RET RET’
next prev parent reply other threads:[~2017-02-20 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 13:18 bug#25751: Query replace lazy highlighting Antoine Levitt
2017-02-16 21:01 ` Juri Linkov
2017-02-16 22:45 ` Juri Linkov
2017-02-17 6:37 ` Eli Zaretskii
2017-02-17 22:52 ` Juri Linkov
2017-02-18 8:13 ` Eli Zaretskii
2017-02-18 23:17 ` Juri Linkov
2017-02-18 23:51 ` Drew Adams
2017-02-20 0:30 ` Juri Linkov [this message]
2017-02-21 23:22 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuj9k8px.fsf@localhost \
--to=juri@linkov.net \
--cc=25751@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--cc=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.