From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18856@debbugs.gnu.org, David Engster <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 13:38:36 -0400 [thread overview]
Message-ID: <jwv4muoumh0.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83fve82lsn.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 28 Oct 2014 18:36:56 +0200")
> I can overcome this problem if I add a call to
> internal-timer-start-idle at the end of compilation-handle-exit.
> Not sure this is TRT, though.
I don't think this is right: as mentioned the issue is not specific to
compilation, so we'd really need to call internal-timer-start-idle from
the code that runs process-filters.
And it implies a different definition of "idle" than the one we've had
so far, so it'd be an incompatible change.
> then I see a single event, BUFFER_SWITCH_EVENT, being reported.
> Should input-pending-p ignore such events?
I think so, yes, because these events are not (consciously) generated by
the user.
Stefan
next prev parent reply other threads:[~2014-10-28 17:38 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 [this message]
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
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
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=jwv4muoumh0.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18856@debbugs.gnu.org \
--cc=deng@randomsample.de \
--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).