From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18856@debbugs.gnu.org, deng@randomsample.de
Subject: bug#18856: 24.4; *grep* output buffer not getting fontified when jit-lock-defer-time is used
Date: Thu, 30 Oct 2014 00:10:19 -0400 [thread overview]
Message-ID: <jwvk33i2oew.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <837fzi1b05.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 30 Oct 2014 05:39:54 +0200")
> You said "_defer_ fontification when the user is waiting for Emacs".
> When user is waiting for Emacs, idle timers won't run, and therefore
> fontifications done in a function that runs off an idle timer will not
> be performed. How does this not fit what you describe?
Your question was:
Indeed, so what's the point of doing that?
where AFAIK "that" referred to "defer fontification when input is pending".
And I explained that the point of deferring fontification only when
input is pending (as opposed to doing it all the time, as in the
current jit-lock-defer-time system) is that we defer less often, more
specifically we only defer "when we know for sure that the user is
waiting for further processing".
>> Same difference: the 1st redisplay redraws almost the whole window, and
>> the second as well because almost none of the text had been
>> fontified earlier.
> The amount of redrawing depends on what portions of the visible text
> are fontified.
That's why I said "because almost none of the text had been
fontified earlier". It's not always true, but the end result is the
same: the double redisplay takes extra time. Does it take exactly twice
the time? Maybe not exactly, but I think that a factor of 2 is a good
enough approximation.
Stefan
prev parent reply other threads:[~2014-10-30 4:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:33 bug#18856: 24.4; *grep* output buffer not getting fontified when jit-lock-defer-time is used David Engster
2014-10-28 16:36 ` Eli Zaretskii
2014-10-28 17:38 ` Stefan Monnier
2014-10-29 15:01 ` Eli Zaretskii
2014-10-29 22:23 ` Stefan Monnier
2014-11-01 14:24 ` Eli Zaretskii
2014-10-28 17:09 ` Stefan Monnier
2014-10-28 17:53 ` Eli Zaretskii
2014-10-28 19:01 ` Stefan Monnier
2014-10-28 19:26 ` Eli Zaretskii
2014-10-29 4:06 ` Stefan Monnier
2014-10-29 14:16 ` Eli Zaretskii
2014-10-29 22:16 ` Stefan Monnier
2014-10-30 3:39 ` Eli Zaretskii
2014-10-30 4:10 ` Stefan Monnier [this message]
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=jwvk33i2oew.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18856@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
/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.