From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: 12937@debbugs.gnu.org
Subject: bug#12937: 24.2; Fontification performed in 'jit-lock-defer-time' in any case (don't wait while Emacs become really idle).
Date: Mon, 19 Nov 2012 22:56:26 +0200 [thread overview]
Message-ID: <87obitia6d.fsf@gavenkoa.example.com> (raw)
I open (a very long .c file):
emacs-bzr/trunk/src/coding.c
and hold DOWN key. Text in buffer scrolls up but with jerks (random stops of
scrolling for a little time) due to fontification actions.
From 'jit-lock-defer-time' docs:
Idle time after which deferred fontification should take place.
If nil, fontification is not deferred.
I would try to workaround jerks with:
(setq jit-lock-defer-time 0.01)
and with same negative effect by (see below):
(setq jit-lock-defer-time 3.0)
When I hold DOWN key text scrolls up with jerks again! Because fontification
performed again.
I expect that when I *hold* key Emacs in not idle (it get user input and
redisplay text!!) so don't understand why fontification take place. May be I
misunderstand idling concept in Emacs and should read manuals deeper...
Also note that fixing CC-mode is not a solution as there are many possible
external modes that can be useful but with slow fontification.
So it is good to have 'jit-lock-defer-time' behaviour that allow trick with
defer fontification.
I know some peoples use workflow when they use scroll-bars for very fast
moving around a file (to get brief look of file content). I prefer use
PageUp/PageDown keys to perform this task.
In GNU Emacs 24.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10)
of 2012-09-09 on trouble, modified by Debian
Windowing system distributor `The X.Org Foundation', version 11.0.11204000
--
Best regards!
next reply other threads:[~2012-11-19 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 20:56 Oleksandr Gavenko [this message]
2012-11-19 21:29 ` bug#12937: 24.2; Fontification performed in 'jit-lock-defer-time' in any case (don't wait while Emacs become really idle) Stefan Monnier
2019-10-30 22:45 ` Lars Ingebrigtsen
2020-04-17 10:24 ` Stefan Kangas
2012-11-20 4:00 ` Eli Zaretskii
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=87obitia6d.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.com \
--cc=12937@debbugs.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.