From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Tue, 28 Oct 2014 19:53:12 +0200 [thread overview]
Message-ID: <838uk02i9j.fsf@gnu.org> (raw)
In-Reply-To: <jwva94gunuu.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Tue, 28 Oct 2014 13:09:02 -0400
> Cc: 18856@debbugs.gnu.org
>
> IOW jit-lock-defer should use a non-idle timer for this case.
But then how do we ensure the fontifications don't happen for as long
as Emacs isn't idle? test idleness by hand inside the timer function?
> Note that an alternative implementation of jit-lock-defer which only
> defers when there is not input pending would supposedly not suffer from
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You mean, when there _is_ input pending, right?
> this problem since it wouldn't defer fontification in this case (of
> course, that would suffer from the reverse problem that by failing to
> defer fontification, the redisplay may not be able to keep up with
> process output).
Indeed, so what's the point of doing that?
next prev parent reply other threads:[~2014-10-28 17:53 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 [this message]
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
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=838uk02i9j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18856@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=monnier@iro.umontreal.ca \
/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.