From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Alan Mackenzie <acm@muc.de>
Cc: 20404@debbugs.gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: bug#20404: 25.0.50; Sometimes no fontification with jit-lock-defer-time
Date: Wed, 22 Apr 2015 13:37:13 -0400 [thread overview]
Message-ID: <jwvwq14f58b.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <20150422163110.68601.qmail@mail.muc.de> (Alan Mackenzie's message of "22 Apr 2015 16:31:10 -0000")
[ OFFTOPIC: the bug report is not about performance but about
a functional bug in jit-lock-defer. ]
> There's a solution (or, depending on your point of view, a workaround)
> for this. You're using Emacs-25, so set fast-but-imprecise-scrolling to
> t, or customize it (it's in customisation group "scrolling").
FWIW, on my machine, this doesn't make much difference: a single
"font-lock one screen's worth" takes much too long, so after that one
screen is displayed, Emacs takes a while catching up (with no display at
all in the mean time).
That's why after you installed your change, I installed the one I had
suggested (which tweaks the decision about when to skip redisplay and
when to defer font-lock and relies on using jit-lock-defer-time).
In my tests, it worked significantly better (was able to keep up).
So I recommend you try jit-lock-defer-time set to 0 instead of using
fast-but-imprecise-scrolling, and see if you like the
resulting behavior.
IIUC if Emacs can *almost* keep up, then fast-but-imprecise-scrolling
might be just enough to let it keep up, in which case the behavior may
look be better than with jit-lock-defer-time (because the text is never
displayed unfontified). But if the repeat rate is faster than that, then
jit-lock-defer-time should give noticeably better results.
Stefan
next prev parent reply other threads:[~2015-04-22 17:37 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvwq14f58b.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=20404@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=tsdh@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.