unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
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: Wed, 29 Oct 2014 18:16:00 -0400	[thread overview]
Message-ID: <jwvwq7i5xui.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83vbn30xmq.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 29 Oct 2014 16:16:29 +0200")

>> >> To only defer fontification when we know "for sure" that the user is
>> >> waiting for further processing.
>> > Sorry, you lost me.  When input is pending, what further processing is
>> > the user waiting for?
>> The user is waiting for Emacs to process the input that he's already sent.
> Using an idle timer does that, right?

Huh?  No, the user is waiting because Emacs hasn't replied yet.
Idle timers are for when the user hasn't given any command, so Emacs is
waiting, rather than the user.

>> The 1st redisplay also only redrew the portion that was modified, which
>> is pretty close in many cases to the portion that later gets fontified.
> I was thinking about scrolling with C-v, in which case the first
> redisplay redraws almost the entire window.

Same difference: the 1st redisplay redraws almost the whole window, and
the second as well because almost none of the text had been
fontified earlier.

You're right, that the amount of redraw is not always exactly the same,
but I think that in many/most cases the two are comparable.


        Stefan





  reply	other threads:[~2014-10-29 22:16 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
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 [this message]
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=jwvwq7i5xui.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).