From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20404@debbugs.gnu.org
Subject: bug#20404: 25.0.50; Sometimes no fontification with jit-lock-defer-time
Date: Wed, 22 Apr 2015 22:32:14 +0200 [thread overview]
Message-ID: <87y4ljgb01.fsf_-_@gnu.org> (raw)
In-Reply-To: <837ft44fnf.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 Apr 2015 13:32:36 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Another and even reproducible case is `report-emacs-bug'. It goes
>> like this:
>>
>> 1. emacs -Q
>> 2. eval my above settings in *scratch*
>> 3. M-x report-emacs-bug
>>
>> The new message buffer is completely unfontified initially. As soon
>> as you move point, font-lock kicks in and the header lines get their
>> proper fontification. Or maybe it's the other way round, i.e., the
>> buffer is created, then redisplayed, then the fontification takes
>> place but no redisplay is performed thereafter.
>
> Sounds like the idle timer that is started by jit-lock-defer-time
> never runs after the buffer is displayed.
Indeed, that's the case. Or wait, it eventually runs but much later
than `jit-lock-defer-time' defines.
> Could it be that it already ran before the display?
No. The bug report buffer is displayed first, and then it takes two or
three seconds until the first jit-lock kicks in. And then the buffer
will be redisplayed and appears fontified.
I tested using this code:
--8<---------------cut here---------------start------------->8---
(progn
(setq jit-lock-defer-time 0.0312
jit-lock-stealth-nice 0.117
jit-lock-stealth-time 0.23)
(require 'cl-lib)
(defvar i 0)
(advice-add 'jit-lock-deferred-fontify :before
(lambda ()
(message "DEFERRED FONTIFY %s" (cl-incf i)))))
--8<---------------cut here---------------end--------------->8---
Bye,
Tassilo
next prev parent reply other threads:[~2015-04-22 20:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 9:45 bug#20404: 25.0.50; Sometimes no fontification with jit-lock-defer-time Tassilo Horn
2015-04-22 10:32 ` Eli Zaretskii
2015-04-22 20:32 ` Tassilo Horn [this message]
2015-04-22 21:39 ` Eli Zaretskii
2015-04-23 5:59 ` Tassilo Horn
2015-04-23 6:14 ` Eli Zaretskii
2015-04-23 8:36 ` Tassilo Horn
[not found] ` <mailman.1344.1429696032.904.bug-gnu-emacs@gnu.org>
2015-04-22 16:31 ` Alan Mackenzie
2015-04-22 17:37 ` Stefan Monnier
2015-04-22 19:32 ` Alan Mackenzie
2015-04-22 20:52 ` Stefan Monnier
2015-04-22 20:10 ` Tassilo Horn
2015-04-22 21:33 ` Eli Zaretskii
2015-04-23 4:15 ` Tassilo Horn
2015-04-23 6:35 ` Eli Zaretskii
2015-04-23 13:40 ` Stefan Monnier
2015-04-23 15:11 ` Eli Zaretskii
2015-04-23 16:23 ` Stefan Monnier
2015-04-23 17:03 ` Eli Zaretskii
2015-04-23 17:27 ` Stefan Monnier
2015-04-23 17:34 ` Eli Zaretskii
2015-04-23 19:35 ` Stefan Monnier
2015-04-24 9:41 ` Eli Zaretskii
2015-04-24 14:03 ` Stefan Monnier
2015-04-24 14:36 ` Eli Zaretskii
2015-04-24 18:03 ` Stefan Monnier
2015-04-23 19:53 ` Tassilo Horn
2015-04-23 17:25 ` Eli Zaretskii
2015-04-23 19:31 ` Stefan Monnier
2015-04-23 19:52 ` Eli Zaretskii
2015-04-23 19:56 ` Tassilo Horn
2015-04-23 7:54 ` Eli Zaretskii
2015-04-23 8:38 ` Eli Zaretskii
2015-04-23 9:04 ` Tassilo Horn
2015-04-23 9:16 ` Eli Zaretskii
2015-04-23 13:40 ` Stefan Monnier
2019-10-31 14:23 ` Lars Ingebrigtsen
2019-10-31 14:51 ` Eli Zaretskii
2015-04-23 8:38 ` Tassilo Horn
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4ljgb01.fsf_-_@gnu.org \
--to=tsdh@gnu.org \
--cc=20404@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).