From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel@gnu.org
Subject: Re: Emacs revision #107149
Date: Mon, 13 Feb 2012 17:18:40 -0500 [thread overview]
Message-ID: <jwvvcnatm6b.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20120213214225.GE26954@acm.acm> (Alan Mackenzie's message of "Mon, 13 Feb 2012 21:42:26 +0000")
> I Don't understand. Why is the forcing of immediate fontification ever
> necessary? That's what JIT lock does, isn't it?
JIT lock is only involved when the buffer is displayed directly.
In htmlfontify or ps-print, we need to fontify the buffer even if it's
not displayed because the output (HTML or Postscript) wants to include
the fact info that font-lock adds.
In the mm-view case it's similar: the buffer itself is not displayed,
instead its content is copied into some other buffer (which uses
another major-mode). We could setup this other buffer so that jit-lock
there is redirected to apply font-lock to the internal buffer after
which the result is copied back into the displayed buffer, but instead
mm-view just font-locks the whole buffer eagerly, which is simpler, tho
it loses the laziness of jit-lock.
Stefan
next prev parent reply other threads:[~2012-02-13 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 23:20 Emacs revision #107149 Alan Mackenzie
2012-02-11 15:56 ` Lars Ingebrigtsen
2012-02-11 18:07 ` Wolfgang Jenkner
2012-02-11 19:59 ` Alan Mackenzie
2012-02-12 20:42 ` Lars Ingebrigtsen
2012-02-12 22:22 ` Alan Mackenzie
2012-02-13 1:00 ` Wolfgang Jenkner
2012-02-13 21:35 ` Alan Mackenzie
2012-02-13 3:15 ` Stefan Monnier
2012-02-13 21:42 ` Alan Mackenzie
2012-02-13 22:18 ` Stefan Monnier [this message]
2012-02-13 21:03 ` Lars Ingebrigtsen
2012-02-13 22:07 ` Alan Mackenzie
2012-02-20 9:51 ` Lars Ingebrigtsen
2012-02-21 15:16 ` Alan Mackenzie
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=jwvvcnatm6b.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).