From: Lars Ingebrigtsen <larsi@gnus.org>
To: Oleksandr Gavenko <gavenkoa@gmail.com>
Cc: 12936@debbugs.gnu.org
Subject: bug#12936: 24.2; Setting 'jit-lock-defer-time' to number prevent some new buffers from automatic fontification.
Date: Wed, 30 Oct 2019 23:40:58 +0100 [thread overview]
Message-ID: <87a79hoo05.fsf@gnus.org> (raw)
In-Reply-To: <87vcd1iep5.fsf@gavenkoa.example.com> (Oleksandr Gavenko's message of "Mon, 19 Nov 2012 21:18:46 +0200")
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> I write to my .emacs:
>
> ;; Increase scrolling speed by defer consuming operation.
> (setq jit-lock-defer-time 0.01)
>
> If I visit some file or create buffer - fontification does not performed until
> I press any key.
>
> For example: "M-x compile make RET" and *compilation* buffer fontified only if
> I press some key after RET. Same with "M-x grep RET" and in another cases.
This was fixed as a special case in compile.el in 2014:
;; Turn off deferred fontifications in the compilation buffer, if
;; the user turned them on globally. This is because idle timers
;; aren't re-run after receiving input from a subprocess, so the
;; buffer is left unfontified after the compilation exits, until
;; some other input event happens.
(set (make-local-variable 'jit-lock-defer-time) nil)
However, removing that does not remove all fontifying, but it seems to
happen only after the compilation process has ended.
So I'm not sure -- there seems to be a general problem here, but is it
something that should be fixed? Or is it up to individual modes (like
compilation mode) to switch delayed fontification off? There's probably
not a lot of these modes that fontify process output on-the-fly.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-30 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 19:18 bug#12936: 24.2; Setting 'jit-lock-defer-time' to number prevent some new buffers from automatic fontification Oleksandr Gavenko
2012-11-19 19:55 ` Stefan Monnier
2019-10-30 22:40 ` Lars Ingebrigtsen [this message]
2021-07-15 17:18 ` Lars Ingebrigtsen
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=87a79hoo05.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12936@debbugs.gnu.org \
--cc=gavenkoa@gmail.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 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).